OCP installation requirement #403
Conversation
| @@ -23,7 +23,7 @@ | |||
| shell: | | |||
| cd {{ ocp_version_path }} | |||
| rm -rf openshift-install-linux-*.tar.gz openshift-client-linux-*.tar.gz | |||
| oc.latest adm release extract --tools {{ ocp_release_image }} | |||
| REGISTRY_AUTH_FILE="$HOME/.docker/config.json" oc.latest adm release extract --tools {{ ocp_release_image }} | |||
README.md
Outdated
| @@ -62,6 +62,7 @@ Versions: | |||
| * ibmcloud plugin install sl (IBMcloud environments) | |||
| * RHEL 8.6 / Rocky 8.6 (Bastion) | |||
| * podman 3 / 4 (Bastion) | |||
| * podman login -u $USER -p $PASSWORD (Bastion) | |||
There was a problem hiding this comment.
I think the issue where you had connection refused was potentially because either the assisted-service api container was either not running and though rerunning the setup-bastion that would have had the container back up and running. Do you have a reproducer of the error so I could check this in my environment? Alternatively if it occurs in your environment again, let me know so I can take a quick peak at the containers status and logs.
There was a problem hiding this comment.
At the beginning I have added REGISTRY_AUTH_FILE="$HOME/.docker/config.json" to solve unauthorized access error when running:
ansible-playbook -i ansible/inventory/ibmcloud.local ansible/ibmcloud-setup-bastion.yml
Then when running:
ansible-playbook -i ansible/inventory/ibmcloud.local ansible/ibmcloud-bm-deploy.yml
Got Request failed: <urlopen error [Errno 111] Connection refused>", "redirected": false, "status": -1, "url": "http://xx.xx.xx.xx:8090/api/assisted-install/v2/clusters"
When running podman login -u $USER -p $PASSWORD, issue is solved.
ebattat
force-pushed
the
ocp_install_requirment
branch
from
543e45f
to
2d61a9c
Compare
Fixes:
error: unable to read image quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256: unauthorized: access to the requested resource is not authorized