Bug 1727318 - e2e-aws-upgrade-rollback-4.1-to-4.2: ClusterOperatorNotAvailable: Cluster operator image-registry is still updating
Summary: e2e-aws-upgrade-rollback-4.1-to-4.2: ClusterOperatorNotAvailable: Cluster ope...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Image Registry
Version: 4.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: ---
: 4.2.0
Assignee: Corey Daley
QA Contact: Wenjing Zheng
URL:
Whiteboard:
: 1727317 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-07-05 14:19 UTC by tflannag
Modified: 2019-10-16 06:33 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-10-16 06:33:09 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift cluster-image-registry-operator pull 311 0 'None' closed bug 1727318: pkg/clusterconfig: use infra.Status.Platform if PlatformStatus is nil 2020-05-26 09:54:50 UTC
Github openshift cluster-image-registry-operator pull 312 0 'None' closed bug 1727318: Revert infrastructure name change 2020-05-26 09:54:50 UTC
Github openshift cluster-image-registry-operator pull 313 0 'None' closed bug 1727318: Revert "Removing dependency on installer and clusterversions" 2020-05-26 09:54:50 UTC
Red Hat Product Errata RHBA-2019:2922 0 None None None 2019-10-16 06:33:19 UTC

Description tflannag 2019-07-05 14:19:52 UTC 
https://storage.googleapis.com/origin-ci-test/logs/release-openshift-origin-installer-e2e-aws-upgrade-rollback-4.1-to-4.2/16/artifacts/e2e-aws-upgrade/pods/openshift-image-registry_cluster-image-registry-operator-7dfbcc46df-f4z68_cluster-image-registry-operator.log
Comment 1 Antonio Murdaca 2019-07-05 14:27:41 UTC 
https://github.com/openshift/cluster-image-registry-operator/pull/311
Comment 2 Ben Parees 2019-07-05 14:33:50 UTC 
(assigning to Corey....Antonio was kind enough to code up a PR but if there are verification issues, Corey owns running it down)
Comment 3 Corey Daley 2019-07-05 16:59:36 UTC 
Pull request has merged to revert the change
https://github.com/openshift/cluster-image-registry-operator/pull/312
Comment 4 Oleg Bulatov 2019-07-09 09:47:34 UTC 
*** Bug 1727317 has been marked as a duplicate of this bug. ***
Comment 6 Wenjing Zheng 2019-07-18 10:28:18 UTC 
I can reproduce when upgrade path is 4.1.4->4.1.6->4.2.0-0.nightly-2019-07-15-231921, below error appears:
Unable to apply resources: unable to sync storage configuration: secret "cluster-config-v1" not found

If upgrade to latest 4.2 payload 4.2.0-0.nightly-2019-07-18-032637, no such error and image-registry upgrade succeeds:
image-registry                             4.2.0-0.nightly-2019-07-18-032637   True        False         False      32m
Comment 7 errata-xmlrpc 2019-10-16 06:33:09 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
Note You need to log in before you can comment on or make changes to this bug.