In a disconnected installation, installer fails with message

Couldn't resolve domain name registry.build05.ci.openshift.org on the host. To continue installation, create the necessary DNS entries to resolve this domain name to your cluster's release image host IP address (see Prow job logs below)

registry.build05.ci.openshift.org is the hostname of the containers registry source, but being a disconnected installation, mirror hostname should be used instead (as per oc adm release mirror command output, see mirroring logs below)

4.14.0-0.nightly-2023-06-13-223353

1/1

1. Prepare for a disconnected installation with ipv6 single stack
2. Start the installation and use log level debug for the wait-for bootstra-complete command
3.

Install fails with message

Couldn't resolve domain name registry.build05.ci.openshift.org on the host. To continue installation, create the necessary DNS entries to resolve this domain name to your cluster's release image host IP address

Install completes resolving container registry mirror's hostname (openshift-qe-055.arm.eng.rdu2.redhat.com, see mirroring logs below)

This is an ipv6 only installation, registry.build05.ci.openshift.org has no v6 support

Prow job https://qe-private-deck-ci.apps.ci.l2s4.p1.openshiftapps.com/view/gs/qe-private-deck/pr-logs/pull/openshift_release/37936/rehearse-37936-periodic-ci-openshift-openshift-tests-private-release-4.14-amd64-nightly-agent-abi-ansible-sno-v6-disconnected-static/1668955603805933568# 

Mirroring logs https://gcsweb-qe-private-deck-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/qe-private-deck/pr-logs/pull/openshift_release/37936/rehearse-37936-periodic-ci-openshift-openshift-tests-private-release-4.14-amd64-nightly-agent-abi-ansible-sno-v6-disconnected-static/1668955603805933568/artifacts/abi-ansible-sno-v6-disconnected-static/baremetal-lab-agent-ansible-install/build-log.txt