Bug 2099663

Summary:	[sig-arch][Early] Managed cluster should start all core operators - Some cluster operators are not ready: ingress
Product:	OpenShift Container Platform	Reporter:	Riccardo Pittau <rpittau>
Component:	Networking	Assignee:	Ben Bennett <bbennett>
Networking sub component:	ovn-kubernetes	QA Contact:	Anurag saxena <anusaxen>
Status:	CLOSED DUPLICATE	Docs Contact:
Severity:	high
Priority:	high	CC:	wking
Version:	4.10
Target Milestone:	---
Target Release:	---
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:	2022-06-22 07:03: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 Riccardo Pittau 2022-06-21 13:01:04 UTC

latest 4.10 nightlies faile because of the error:
" [sig-arch][Early] Managed cluster should start all core operators [Skipped:Disconnected] [Suite:openshift/conformance/parallel] expand_less	2s
{  fail [github.com/onsi/ginkgo.0-origin.0+incompatible/internal/leafnodes/runner.go:113]: Jun 14 23:20:50.700: Some cluster operators are not ready: ingress (Upgradeable=False IngressControllersNotUpgradeable: Some ingresscontrollers are not upgradeable: ingresscontroller "default" is not upgradeable: OperandsNotUpgradeable: One or more managed resources are not upgradeable: load balancer service has been modified; changes must be reverted before upgrading: )}"

in gcp-ovn-upgrade-4.10-minor job

an example:
https://openshift-release.apps.ci.l2s4.p1.openshiftapps.com/releasestream/4.10.0-0.nightly/release/4.10.0-0.nightly-2022-06-16-134011

Comment 2 W. Trevor King 2022-06-21 18:43:54 UTC

Sounds like a dup of bug 2097735 to me.

Comment 3 Riccardo Pittau 2022-06-22 07:03:35 UTC


*** This bug has been marked as a duplicate of bug 2097735 ***