Configuration-based installation of OpenShift and Cloud Pak for Data/Integration/Watson AIOps on various private and public cloud infrastructure providers. Deployment attempts to achieve the end-state defined in the configuration. If something fails along the way, you only need to restart the process to continue the deployment.
Describe the bug
While running the Deployer on AWS IPI, the AWS command to describe availability zones is failing
To Reproduce
Follow standard instructions to create a Bastion, installk Git and pull the deployer code
Run ./cp-deploy.sh build
Add config .yaml files
Run ./cp-deploy.sh env apply --accept-all-licenses
Expected behavior
Deployer should start to create AWS VPC and other objects
Wednesday 15 May 2024 11:27:50 +0000 (0:00:00.523) 0:00:42.928 *****
===============================================================================
lint-config : filter the vault variables from ansible variables --------- 1.57s
lint-config : Run the linter and pre-processor script for object cp4d --- 1.10s
merge-config : Generate config through template ------------------------- 0.96s
vault-get-secret : Create file with secret ------------------------------ 0.89s
lint-config : Run the linter and pre-processor script for object openshift --- 0.87s
lint-config : Run the linter and pre-processor script for object nfs_server --- 0.84s
record-deployer-state : Starting background task to record deployer state in /root/cpd-status/log --- 0.76s
merge-config : Lookup *.yaml files in /root/cpd-config/config ----------- 0.69s
merge-config : Get stats of /root/cpd-config/config --------------------- 0.66s
merge-config : Generate config through template ------------------------- 0.60s
====================================================================================
Deployer FAILED. Check previous messages. If command line is not returned, press ^C.`
Describe the bug While running the Deployer on AWS IPI, the AWS command to describe availability zones is failing
To Reproduce Follow standard instructions to create a Bastion, installk Git and pull the deployer code Run
./cp-deploy.sh build
Add config .yaml files Run./cp-deploy.sh env apply --accept-all-licenses
Expected behavior Deployer should start to create AWS VPC and other objects
Actual behaviour
`TASK [aws-get-zones : Gather availabily zones for region ap-southeast-2] * Wednesday 15 May 2024 11:27:50 +0000 (0:00:00.058) 0:00:42.404 *** fatal: [localhost]: FAILED! => changed=true cmd: |- aws ec2 describe-availability-zones \ --region ap-southeast-2 \ --query "AvailabilityZones[*].ZoneName" delta: '0:00:00.006860' end: '2024-05-15 11:27:50.736225' msg: non-zero return code rc: 127 start: '2024-05-15 11:27:50.729365' stderr: '/bin/sh: line 1: aws: command not found' stderr_lines:
stdout: ''
stdout_lines:
PLAY RECAP ***** localhost : ok=311 changed=8 unreachable=0 failed=1 skipped=135 rescued=0 ignored=0
Wednesday 15 May 2024 11:27:50 +0000 (0:00:00.523) 0:00:42.928 ***** =============================================================================== lint-config : filter the vault variables from ansible variables --------- 1.57s lint-config : Run the linter and pre-processor script for object cp4d --- 1.10s merge-config : Generate config through template ------------------------- 0.96s vault-get-secret : Create file with secret ------------------------------ 0.89s lint-config : Run the linter and pre-processor script for object openshift --- 0.87s lint-config : Run the linter and pre-processor script for object nfs_server --- 0.84s record-deployer-state : Starting background task to record deployer state in /root/cpd-status/log --- 0.76s merge-config : Lookup *.yaml files in /root/cpd-config/config ----------- 0.69s merge-config : Get stats of /root/cpd-config/config --------------------- 0.66s merge-config : Generate config through template ------------------------- 0.60s
==================================================================================== Deployer FAILED. Check previous messages. If command line is not returned, press ^C.`