Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1909527

Summary:	[IPI Baremetal] After upgrade from 4.6 to 4.7 metal3 pod does not get created
Product:	OpenShift Container Platform	Reporter:	Ori Michaeli <omichael>
Component:	Installer	Assignee:	Beth White <beth.white>
Installer sub component:	OpenShift on Bare Metal IPI	QA Contact:	Ori Michaeli <omichael>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	high
Priority:	urgent	CC:	lshilin, omichael, rbartal, sdasu, ssmolyak
Version:	4.7	Keywords:	Triaged, UpcomingSprint
Target Milestone:	---
Target Release:	4.7.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-02-24 15:47:16 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1906105

Description Ori Michaeli 2020-12-20 17:53:21 UTC

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

Comment 2 sdasu 2021-01-06 17:30:34 UTC

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?

Comment 3 Ori Michaeli 2021-01-07 10:29:57 UTC

(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.

Comment 5 Ori Michaeli 2021-01-10 13:10:36 UTC

Verified with upgrade to 4.7.0-0.nightly-2021-01-10-070949

Comment 8 errata-xmlrpc 2021-02-24 15:47:16 UTC

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