Bug 2093462

Summary:	Ingress Operator isn't reconciling the ingress cluster operator object
Product:	OpenShift Container Platform	Reporter:	Grant Spence <gspence>
Component:	Networking	Assignee:	Miciah Dashiel Butler Masters <mmasters>
Networking sub component:	router	QA Contact:	Hongan Li <hongli>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	low
Priority:	medium	CC:	aos-bugs, mmasters
Version:	4.11
Target Milestone:	---
Target Release:	4.11.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	Cause: The ingress operator didn't watch for updates to its clusteroperator object. Consequence: If a user modified or deleted the clusteroperator object, the operator didn't restore it unless some unrelated event triggered reconciliation. Fix: A watch was added on the clusteroperator resource. Result: The ingress operator now immediately restores the clusteroperator object as necessary should something else update or delete it.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-08-10 11:16:18 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 Grant Spence 2022-06-03 19:17:39 UTC

Description of problem:
The ingress operator isn't watching or reconciling when it's cluster operator object is deleted or updated. That means the cluster operator CRD can be deleted by something else and never recreated.

OpenShift release version:
4.11

Cluster Platform:
All

How reproducible:
Always

Steps to Reproduce (in detail):
1. Delete the cluster operator: oc delete clusteroperators.config.openshift.io -n openshift-ingress ingress


Actual results:
The cluster operator doesn't come back.

Expected results:
The cluster operator get recreated.

Impact of the problem:
The cluster operator object can get deleted and never come back.

Additional info:



** Please do not disregard the report template; filling the template out as much as possible will allow us to help you. Please consider attaching a must-gather archive (via `oc adm must-gather`). Please review must-gather contents for sensitive information before attaching any must-gathers to a bugzilla report.  You may also mark the bug private if you wish.

Comment 4 Hongan Li 2022-06-27 02:13:01 UTC

verified with 4.11.0-0.nightly-2022-06-25-081133 and passed

$ oc get clusteroperators.config.openshift.io ingress -n openshift-ingress
NAME      VERSION                              AVAILABLE   PROGRESSING   DEGRADED   SINCE   MESSAGE
ingress   4.11.0-0.nightly-2022-06-25-081133   True        False         False      20m     

$ oc delete clusteroperators.config.openshift.io ingress
clusteroperator.config.openshift.io "ingress" deleted

$ oc get clusteroperators.config.openshift.io ingress
NAME      VERSION                              AVAILABLE   PROGRESSING   DEGRADED   SINCE   MESSAGE
ingress   4.11.0-0.nightly-2022-06-25-081133   True        False         False      28s

Comment 6 errata-xmlrpc 2022-08-10 11:16:18 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 (Important: OpenShift Container Platform 4.11.0 bug fix and security 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-2022:5069