Description of problem: Bootstrap of cluster never completes for vsphere UPI test: https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/logs/release-openshift-ocp-installer-e2e-vsphere-upi-4.4/563 How reproducible: Failed e2e Steps to Reproduce: 1. Run release-openshift-ocp-installer-e2e-vsphere-upi-4.4 test Actual results: Test fails Expected results: Test should pass Additional info: It seems that workers and masters are getting an empty hostname in the ignition URL (see screenshot images): https://storage.googleapis.com/origin-ci-test/logs/release-openshift-ocp-installer-e2e-vsphere-upi-4.4/563/artifacts/e2e-vsphere-upi/installer/compute-0.png https://storage.googleapis.com/origin-ci-test/logs/release-openshift-ocp-installer-e2e-vsphere-upi-4.4/563/artifacts/e2e-vsphere-upi/installer/control-plane-0.png
*** Bug 1797508 has been marked as a duplicate of this bug. ***
Checked latest ci job https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/logs/release-openshift-ocp-installer-e2e-vsphere-upi-4.4/563, the job still failed, but it's not the same with the error described in this bug. Should be another known issue https://bugzilla.redhat.com/show_bug.cgi?id=1798945. And the problem that an empty hostname in the ignition URL is fixed now. https://storage.googleapis.com/origin-ci-test/logs/release-openshift-ocp-installer-e2e-vsphere-upi-4.4/767/artifacts/e2e-vsphere-upi/installer/control-plane-0.png https://storage.googleapis.com/origin-ci-test/logs/release-openshift-ocp-installer-e2e-vsphere-upi-4.4/767/artifacts/e2e-vsphere-upi/installer/compute-0.png Master node and compute node lunched successfully. So verify this bug since original issue has been fixed, and continue track the new failure in bz#1798945
For CI this also needs to change: https://github.com/openshift/release/pull/7096
(In reply to Joseph Callen from comment #3) > For CI this also needs to change: > https://github.com/openshift/release/pull/7096 @Joseph Callen Is the pr for this bug? And should i checked the change in the latest ci job?
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:0581
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days