During upgrade of a cluster in CI build farm, we have seen a sequence of alerts and messages of failures from clusterversion. oc --context build01 adm upgrade --allow-explicit-upgrade --to-image registry.svc.ci.openshift.org/ocp/release:4.3.0-0.nightly-2020-04-13-190424 --force=true Eventually upgrade was completed successfully (which is so nice). But those alerts and messages are too frightening. I would like to create a bug for each of those and feel better for the next upgrade. https://coreos.slack.com/archives/CHY2E1BL4/p1587058244434700 Every 10.0s: oc --context build01 get clusterversions.config.openshift.io Hongkais-MacBook-Pro: Thu Apr 16 13:30:20 2020 NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.3.0-0.nightly-2020-03-23-130439 True True 27m Unable to apply 4.3.0-0.nightly-2020-04-13-190 424: the cluster operator network has not yet successfully rolled out
It's not the networking component's fault that they were unable to complete their whole update and bump their ClusterOperator status within ~5m of the CVO telling them to start (by bumping their operator's Deployment). If there's a comfort-level fix for this issue, it will be on the CVO side softening the "Unable to apply" to suggest "and that may be fine, or maybe not, depending on how long it goes on for".
*** Bug 1825008 has been marked as a duplicate of this bug. ***
Setting the severity to low as this does not effect the cluster functionality.
We do not have time to fix the bug in this sprint as we are working on higher priority bugs and features. Hence we are adding UpcomingSprint now, and we'll revisit the next sprint.
We do not have time to fix the bug in this sprint as we are working on higher priority bugs and features. Hence we are adding UpcomingSprint now, and we'll revisit this in the next sprint.
Moving this to 4.7 as this is not a blocker for 4.6.
I still think we can wordsmith this per comment 2, but I agree that this is cosmetic per comment 4. Hopefully we'll have time to adjust the wording next sprint.
Commen 9 is still current.
(In reply to W. Trevor King from comment #2) > If there's a comfort-level fix for this issue, it will be on the CVO side > softening the "Unable to apply" to suggest "and that may be fine, or maybe > not, depending on how long it goes on for". Ah, I'm going to close this as a dup of bug 1884334. We don't need to soften the wording if we stop setting Failing=True just because an operator is slow. And that bug is part of an ongoing effort to ease ourselves into allowing operators to take as long as they want, and only going Failing=True on them if they set something concerning like Available=False. *** This bug has been marked as a duplicate of bug 1884334 ***