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.
In the disconnected (high side) environment, when using:
cd cloud-pak-deployer
./cp-deploy.sh env apply --skip-mirror-images
We get errors about trying to download CASE files from github:
fatal: [localhost]: FAILED! => {"attempts": 5, "changed": true, "cmd": "oc ibm-pak get ibm-cp-common-services --version 4.3.0 --disable-top-level-images-mode\n", "delta": "0:03:35.939665", "end": "2024-01-18 17:13:54.676715", "msg": "non-zero return code", "rc": 1, "start": "2024-01-18 17:10:18.737050", "stderr": "[WARNING]: Download operation timed out Get \"https://github.com/IBM/cloud-pak/raw/master/repo/case/index.yaml\": dial tcp 140.82.121.4:443: i/o timeout. Retrying...\n[WARNING]: Download operation timed out Get \"https://github.com/IBM/cloud-pak/raw/master/repo/case/index.yaml\": dial tcp 140.82.121.4:443: i/o timeout. Retrying...\n[WARNING]: Download operation timed out Get \"https://github.com/IBM/cloud-pak/raw/master/repo/case/index.yaml\": dial tcp 140.82.121.3:443: i/o timeout. Retrying...\n[ERROR]: unable to obtain root index for 'https://github.com/IBM/cloud-pak/raw/master/repo/case': \"A HTTP processing related error occurred while accessing CASE repo: download operation timed out. Timeout duration can be increased by setting higher value of IBMPAK_HTTP_TIMEOUT. Retry attempts can be increased by setting a higher value of IBMPAK_HTTP_RETRY.\"\nError: Unable to obtain a valid CASE for the CASE name of \"ibm-cp-common-services\" at repository \"https://github.com/IBM/cloud-pak/raw/master/repo/case\" with version \"4.3.0\".\nReview this additional debug information: \"Unable to find a valid CaseDescriptor in the provided repository [\\\"https://github.com/IBM/cloud-pak/raw/master/repo/case\\\" \\\"ibm-cp-common-services\\\" \\\"4.3.0\\\"] A HTTP processing related error occurred while accessing CASE repo: download operation timed out. Timeout duration can be increased by setting higher value of IBMPAK_HTTP_TIMEOUT. Retry attempts can be increased by setting a higher value of IBMPAK_HTTP_RETRY.)\"", "stderr_lines": ["[WARNING]: Download operation timed out Get \"https://github.com/IBM/cloud-pak/raw/master/repo/case/index.yaml\": dial tcp 140.82.121.4:443: i/o timeout. Retrying...", "[WARNING]: Download operation timed out Get \"https://github.com/IBM/cloud-pak/raw/master/repo/case/index.yaml\": dial tcp 140.82.121.4:443: i/o timeout. Retrying...", "[WARNING]: Download operation timed out Get \"https://github.com/IBM/cloud-pak/raw/master/repo/case/index.yaml\": dial tcp 140.82.121.3:443: i/o timeout. Retrying...", "[ERROR]: unable to obtain root index for 'https://github.com/IBM/cloud-pak/raw/master/repo/case': \"A HTTP processing related error occurred while accessing CASE repo: download operation timed out. Timeout duration can be increased by setting higher value of IBMPAK_HTTP_TIMEOUT. Retry attempts can be increased by setting a higher value of IBMPAK_HTTP_RETRY.\"", "Error: Unable to obtain a valid CASE for the CASE name of \"ibm-cp-common-services\" at repository \"https://github.com/IBM/cloud-pak/raw/master/repo/case\" with version \"4.3.0\".", "Review this additional debug information: \"Unable to find a valid CaseDescriptor in the provided repository [\\\"https://github.com/IBM/cloud-pak/raw/master/repo/case\\\" \\\"ibm-cp-common-services\\\" \\\"4.3.0\\\"] A HTTP processing related error occurred while accessing CASE repo: download operation timed out. Timeout duration can be increased by setting higher value of IBMPAK_HTTP_TIMEOUT. Retry attempts can be increased by setting a higher value of IBMPAK_HTTP_RETRY.)\""], "stdout": "CASE repository: case_source (https://github.com/IBM/cloud-pak/raw/master/repo/case)", "stdout_lines": ["CASE repository: case_source (https://github.com/IBM/cloud-pak/raw/master/repo/case)"]}
We talked with @fketelaars on Webex and agreed this is a bug in automation-roles/50-install-cloud-pak/cpfs/cp-fs-cluster-components/tasks/main.yml and a test patch was generated. We have tested the patch and can confirm it works.
Raising this issue to to track the fix delivery for this patch.
In the disconnected (high side) environment, when using:
We get errors about trying to download CASE files from github:
fatal: [localhost]: FAILED! => {"attempts": 5, "changed": true, "cmd": "oc ibm-pak get ibm-cp-common-services --version 4.3.0 --disable-top-level-images-mode\n", "delta": "0:03:35.939665", "end": "2024-01-18 17:13:54.676715", "msg": "non-zero return code", "rc": 1, "start": "2024-01-18 17:10:18.737050", "stderr": "[WARNING]: Download operation timed out Get \"https://github.com/IBM/cloud-pak/raw/master/repo/case/index.yaml\": dial tcp 140.82.121.4:443: i/o timeout. Retrying...\n[WARNING]: Download operation timed out Get \"https://github.com/IBM/cloud-pak/raw/master/repo/case/index.yaml\": dial tcp 140.82.121.4:443: i/o timeout. Retrying...\n[WARNING]: Download operation timed out Get \"https://github.com/IBM/cloud-pak/raw/master/repo/case/index.yaml\": dial tcp 140.82.121.3:443: i/o timeout. Retrying...\n[ERROR]: unable to obtain root index for 'https://github.com/IBM/cloud-pak/raw/master/repo/case': \"A HTTP processing related error occurred while accessing CASE repo: download operation timed out. Timeout duration can be increased by setting higher value of IBMPAK_HTTP_TIMEOUT. Retry attempts can be increased by setting a higher value of IBMPAK_HTTP_RETRY.\"\nError: Unable to obtain a valid CASE for the CASE name of \"ibm-cp-common-services\" at repository \"https://github.com/IBM/cloud-pak/raw/master/repo/case\" with version \"4.3.0\".\nReview this additional debug information: \"Unable to find a valid CaseDescriptor in the provided repository [\\\"https://github.com/IBM/cloud-pak/raw/master/repo/case\\\" \\\"ibm-cp-common-services\\\" \\\"4.3.0\\\"] A HTTP processing related error occurred while accessing CASE repo: download operation timed out. Timeout duration can be increased by setting higher value of IBMPAK_HTTP_TIMEOUT. Retry attempts can be increased by setting a higher value of IBMPAK_HTTP_RETRY.)\"", "stderr_lines": ["[WARNING]: Download operation timed out Get \"https://github.com/IBM/cloud-pak/raw/master/repo/case/index.yaml\": dial tcp 140.82.121.4:443: i/o timeout. Retrying...", "[WARNING]: Download operation timed out Get \"https://github.com/IBM/cloud-pak/raw/master/repo/case/index.yaml\": dial tcp 140.82.121.4:443: i/o timeout. Retrying...", "[WARNING]: Download operation timed out Get \"https://github.com/IBM/cloud-pak/raw/master/repo/case/index.yaml\": dial tcp 140.82.121.3:443: i/o timeout. Retrying...", "[ERROR]: unable to obtain root index for 'https://github.com/IBM/cloud-pak/raw/master/repo/case': \"A HTTP processing related error occurred while accessing CASE repo: download operation timed out. Timeout duration can be increased by setting higher value of IBMPAK_HTTP_TIMEOUT. Retry attempts can be increased by setting a higher value of IBMPAK_HTTP_RETRY.\"", "Error: Unable to obtain a valid CASE for the CASE name of \"ibm-cp-common-services\" at repository \"https://github.com/IBM/cloud-pak/raw/master/repo/case\" with version \"4.3.0\".", "Review this additional debug information: \"Unable to find a valid CaseDescriptor in the provided repository [\\\"https://github.com/IBM/cloud-pak/raw/master/repo/case\\\" \\\"ibm-cp-common-services\\\" \\\"4.3.0\\\"] A HTTP processing related error occurred while accessing CASE repo: download operation timed out. Timeout duration can be increased by setting higher value of IBMPAK_HTTP_TIMEOUT. Retry attempts can be increased by setting a higher value of IBMPAK_HTTP_RETRY.)\""], "stdout": "CASE repository: case_source (https://github.com/IBM/cloud-pak/raw/master/repo/case)", "stdout_lines": ["CASE repository: case_source (https://github.com/IBM/cloud-pak/raw/master/repo/case)"]}We talked with @fketelaars on Webex and agreed this is a bug in
automation-roles/50-install-cloud-pak/cpfs/cp-fs-cluster-components/tasks/main.ymland a test patch was generated. We have tested the patch and can confirm it works.Raising this issue to to track the fix delivery for this patch.