Bug 1743257

Summary:	Monitoring operator is flapping the upgradeable status
Product:	OpenShift Container Platform	Reporter:	Michal Fojtik <mfojtik>
Component:	Monitoring	Assignee:	Lili Cosic <lcosic>
Status:	CLOSED ERRATA	QA Contact:	Junqi Zhao <juzhao>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	4.2.0	CC:	alegrand, anpicker, erooth, lcosic, mloibl, pkrupa, surbania
Target Milestone:	---
Target Release:	4.2.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:	2019-10-16 06:36:23 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 Michal Fojtik 2019-08-19 13:29:41 UTC

Description of problem:

In 4.2.x/master the monitoring operator is flapping the upgradeable=true/false condition every 5 minutes.

It sets the `reason: RollOutInProgress` and make upgradeable=false and remove the versions from status field. Then it put it back and repeat that one more time.
Then everything is set back to original state and this repeats every 5 minutes.


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Lili Cosic 2019-08-19 13:36:40 UTC

This seems to be in sync with our reconcile loop. As discussed on slack with brancz, we might not want to set it NotUpgradeable every-time we reconcile. WDYT Serg?

Comment 2 Michal Fojtik 2019-08-19 14:08:58 UTC

You should also not flap the status in your CR every 5 minutes. The only operator that does the same (and it will be fixed) is the machine-api operator today.

Comment 7 errata-xmlrpc 2019-10-16 06:36:23 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, 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/RHBA-2019:2922

Comment 8 Red Hat Bugzilla 2023-09-14 05:41:54 UTC

The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days