Bug 1727318
| Summary: | e2e-aws-upgrade-rollback-4.1-to-4.2: ClusterOperatorNotAvailable: Cluster operator image-registry is still updating | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | tflannag |
| Component: | Image Registry | Assignee: | Corey Daley <cdaley> |
| Status: | CLOSED ERRATA | QA Contact: | Wenjing Zheng <wzheng> |
| Severity: | urgent | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 4.2.0 | CC: | amurdaca, aos-bugs, bparees, cdaley, jokerman, mmccomas, obulatov |
| 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:33:09 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
tflannag
2019-07-05 14:19:52 UTC
(assigning to Corey....Antonio was kind enough to code up a PR but if there are verification issues, Corey owns running it down) Pull request has merged to revert the change https://github.com/openshift/cluster-image-registry-operator/pull/312 *** Bug 1727317 has been marked as a duplicate of this bug. *** 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 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 |