Can`t install BlueXP on-prem on EC2 instance with IMDS disabled

Last updated
Save as PDF
Share
1. Share
2. Tweet

Views:

Visibility:: Public

Votes:: 0

Category:: cloud-manager

Specialty:: CLOUD

Last Updated:

Applies to

NetApp BlueXP (formerly Cloud Manager)
Amazon EC2
IMDSv1

Issue

Tying to install BlueXP on-prem version on EC2 instance in AWS and the service-manager.log contains the following errors:

Nov 21 16:14:07 ip-xx-xx-xxx-xx sm2: 2022-11-21T16:14:07.974Z #033[32minfo#033[39m: [+] Pulling cloudmanager_credentials cloudmanagerinfraprod.azurecr.io/cloudmanager_credentials:dfa14cc-47-S

Nov 21 16:14:37 ip-xx-xx-xxx-xx sm2: 2022-11-21T16:14:37.021Z #033[32minfo#033[39m: [+] Starting services

Nov 21 16:14:38 ip-xx-xx-xxx-xx dockerd: time="2022-11-21T16:14:38.237097485Z" level=warning msg="failed to prune image cloudmanagerinfraprod.azurecr.io/cloudmanager_traefik@sha256:9005a79dd96f575f89d7142e21ed2c1ff6dd2c4a9f77c7a7307fc08a99f18db9: No such image: cloudmanagerinfraprod.azurecr.io/cloudmanager_traefik@sha256:9005a79dd96f575f89d7142e21ed2c1ff6dd2c4a9f77c7a7307fc08a99f18db9"

Nov 21 16:14:38 ip-xx-xx-xxx-xx dockerd: time="2022-11-21T16:14:38.323387387Z" level=warning msg="failed to prune image cloudmanagerinfraprod.azurecr.io/cloudmanager_static-file-server@sha256:5bfcfd7bc16e47eed3fdc078511d688a375847c4350859b743043149b9e0d346: No such image: cloudmanagerinfraprod.azurecr.io/cloudmanager_static-file-server@sha256:5bfcfd7bc16e47eed3fdc078511d688a375847c4350859b743043149b9e0d346"

Nov 21 16:14:38 ip-xx-xx-xxx-xx dockerd: time="2022-11-21T16:14:38.798676945Z" level=warning msg="failed to prune image cloudmanagerinfraprod.azurecr.io/cloudmanager_credentials@sha256:eb048a4df393c90b2c1d85e8cab1696e2788fe70cbc604cb812f37e0efe7f32d: No such image: cloudmanagerinfraprod.azurecr.io/cloudmanager_credentials@sha256:eb048a4df393c90b2c1d85e8cab1696e2788fe70cbc604cb812f37e0efe7f32d"

Nov 21 16:14:38 ip-xx-xx-xxx-xx sm2: 2022-11-21T16:14:38.802Z #033[31merror#033[39m: [-] docker-compose up status 1 The Compose file './docker-compose.yml' is invalid because:

Nov 21 16:14:38 ip-xx-xx-xxx-xx sm2: Unsupported config option for services: 'cloudmanager_traefik'

Nov 21 16:14:38 ip-xx-xx-xxx-xx sm2: Unsupported config option for volumes: 'cloudmanager_traefik_certs'

Nov 21 16:14:38 ip-xx-xx-xxx-xx sm2: Unsupported config option for networks: 'connector-network'

Nov 21 16:14:38 ip-xx-xx-xxx-xx sm2: 2022-11-21T16:14:38.803Z #033[31merror#033[39m: docker-compose up failed with status 1

Nov 21 16:14:38 ip-xx-xx-xxx-xx sm2: 2022-11-21T16:14:38.803Z #033[31merror#033[39m: Error: docker-compose up failed with status 1

Nov 21 16:14:38 ip-xx-xx-xxx-xx sm2: at mainLoop (/snapshot/sm2dist/bundle.js)

Nov 21 16:14:38 ip-xx-xx-xxx-xx sm2: at runMicrotasks (<anonymous>)

Nov 21 16:14:38 ip-xx-xx-xxx-xx sm2: at processTicksAndRejections (node:internal/process/task_queues:96:5)

Nov 21 16:14:38 ip-xx-xx-xxx-xx sm2: at async /snapshot/sm2dist/bundle.js```

The server.log file may also contain the followoing error:

com.amazonaws.SdkClientException: The requested metadata is not found at http://169.254.169.254/latest/meta-data/iam/info