Version: Upgrade from 4.6 to 4.7.0-0.nightly-2020-12-20-055006 $ ./openshift-baremetal-install version ./openshift-baremetal-install 4.7.0-0.nightly-2020-12-20-055006 built from commit e235783fe671864e0628771d0e5d13904e4d062a release image registry.ocp-edge-cluster-0.qe.lab.redhat.com:5000/localimages/local-release-image@sha256:ea2d954b1ac4b2818c419055afdb9ff87c5b95fa03c3258a26dc542f4ecab5d8 Platform: IPI BM What happened? After upgrade from 4.6 to 4.7 nightly, metal3 pod is missing. What did you expect to happen? Metal3 pod to get created after the upgrade. How to reproduce it (as minimally and precisely as possible)? 1. Mirror release image to the disconnected registry. 2. Create ImageContentSourcePolicy. 3. Create ConfigMap for image signature. 4. Create custom upgrade graph. 5. Point CVO to custom upgrade graph. 6. Upgrade to 4.7 nightly. Anything else we need to know? I will attach must-gather
The "How to reproduce it" section it does not specifically mention the use of dev-scripts in the steps. But, looking at the must-gather logs it appears that dev-scripts was used. Could you please confirm?
(In reply to sdasu from comment #2) > The "How to reproduce it" section it does not specifically mention the use > of dev-scripts in the steps. But, looking at the must-gather logs it appears > that dev-scripts was used. Could you please confirm? I did not use dev-scripts.
Verified with upgrade to 4.7.0-0.nightly-2021-01-10-070949
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 (Moderate: OpenShift Container Platform 4.7.0 security, bug fix, and enhancement update), 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/RHSA-2020:5633