Bug 1825008 - [4.3 upgrade][clusterverion]the cluster operator machine-config has not yet successfully rolled out
Summary: [4.3 upgrade][clusterverion]the cluster operator machine-config has not yet s...
Keywords:
Status: CLOSED DUPLICATE of bug 1825006
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Machine Config Operator
Version: 4.3.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Antonio Murdaca
QA Contact: Michael Nguyen
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-04-16 20:10 UTC by Hongkai Liu
Modified: 2020-04-16 21:59 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-04-16 21:59:48 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Hongkai Liu 2020-04-16 20:10:13 UTC 
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/p1587060451460800

Every 10.0s: oc --context build01 get clusterversions.config.openshift.io       Hongkais-MacBook-Pro: Thu Apr 16 14:05:58 2020
NAME      VERSION                             AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.3.0-0.nightly-2020-03-23-130439   True        True          62m     Unable to apply 4.3.0-0.nightly-2020-04-13-190
424: the cluster operator machine-config has not yet successfully rolled out

must-gather after upgrade:
http://file.rdu.redhat.com/~hongkliu/test_result/upgrade/upgrade0416/aaa/
Comment 1 W. Trevor King 2020-04-16 21:59:48 UTC 

*** This bug has been marked as a duplicate of bug 1825006 ***
Note You need to log in before you can comment on or make changes to this bug.