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:
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?
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.
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
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days