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

Bug 1892620

Summary:	[IPI Baremetal] Upgrade from 4.6.1 to 4.7 nightly is stuck on "the cluster operator network has not yet successfully rolled out"
Product:	OpenShift Container Platform	Reporter:	Ori Michaeli <omichael>
Component:	Networking	Assignee:	Aniket Bhat <anbhat>
Networking sub component:	openshift-sdn	QA Contact:	zhaozhanqi <zzhao>
Status:	CLOSED DUPLICATE	Docs Contact:
Severity:	medium
Priority:	medium	CC:	aos-bugs, bbennett, jokerman, kiran, omichael, wking
Version:	4.6
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:	2020-11-09 19:42:35 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:

Description Ori Michaeli 2020-10-29 10:45:21 UTC

Version:
Upgrade from 4.6.1 to 4.7.0-0.nightly-2020-10-27-051128

$ ./openshift-install version
./openshift-baremetal-install 4.7.0-0.nightly-2020-10-27-051128
built from commit de62b01d451857d942ac41dcfdad9385856fde9e
release image registry.ocp-edge-cluster-0.qe.lab.redhat.com:5000/localimages/local-release-image@sha256:2945b52c8bf58f18a2770071acb8cece1fad38c105f28c98dbfecfe675e2f758

Platform:

IPI Baremetal

What happened?

Upgrade procedure stuck on "the cluster operator network has not yet successfully rolled out"

What did you expect to happen?

Upgrade procedure to pass successfully.

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 W. Trevor King 2020-11-03 22:55:48 UTC

CVO is pretty clearly pointing at the network operator being the blocker.  Re-assigning to the network folks, who can punt it back to us if they think the cluster-version operator is somehow mangling our handling of their release-image manifests.

Comment 3 Ben Bennett 2020-11-05 14:09:01 UTC

Assigning to the development branch to investigate.  We will consider the backport when the issue is understood.