Bug 1726296
| Summary: | e2e-aws-upgrade-rollback-4.1-to-4.2 failure: Cluster operator machine-config is still updating | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Samuel Padgett <spadgett> |
| Component: | Machine Config Operator | Assignee: | Antonio Murdaca <amurdaca> |
| Status: | CLOSED ERRATA | QA Contact: | Micah Abbott <miabbott> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 4.2.0 | ||
| 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:32:48 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
Samuel Padgett
2019-07-02 14:07:18 UTC
This is a 4.1.x -> 4.2 issue so testing should be spin up a 4.1 cluster and upgrade it to 4.2 The PR above had a bug, this one fully takes care of the bug: https://github.com/openshift/machine-config-operator/pull/913 Notes for testing: - install 4.1.x - grab any 4.2 nightly or payload that includes the above PRs - run an upgrade The above results in a success upgrade (tested myself manually) Verified upgrading from 4.1.7 to 4.2.0-0.nightly-2019-07-30-073644
```
$ oc get clusterversion
NAME VERSION AVAILABLE PROGRESSING SINCE STATUS
version 4.1.7 True False 8s Cluster version is 4.1.7
$ oc patch clusterversion/version --patch '{"spec":{"upstream":"https://openshift-release.svc.ci.openshift.org/graph"}}' --type=merge
clusterversion.config.openshift.io/version patched
$ oc adm upgrade --force --to-image=registry.svc.ci.openshift.org/ocp/release:4.2.0-0.nightly-2019-07-30-073644
Updating to release image registry.svc.ci.openshift.org/ocp/release:4.2.0-0.nightly-2019-07-30-073644
$ oc get clusterversion
NAME VERSION AVAILABLE PROGRESSING SINCE STATUS
version 4.1.7 True True 1s Working towards registry.svc.ci.openshift.org/ocp/release:4.2.0-0.nightly-2019-07-30-073644: downloading update
$ oc get clusterversion
NAME VERSION AVAILABLE PROGRESSING SINCE STATUS
version 4.1.7 True True 5m53s Working towards 4.2.0-0.nightly-2019-07-30-073644: 24% complete
$ oc get clusterversion
NAME VERSION AVAILABLE PROGRESSING SINCE STATUS
version 4.1.7 True True 10m Working towards 4.2.0-0.nightly-2019-07-30-073644: 83% complete
$ oc get clusterversion
NAME VERSION AVAILABLE PROGRESSING SINCE STATUS
version 4.2.0-0.nightly-2019-07-30-073644 True False 16h Cluster version is 4.2.0-0.nightly-2019-07-30-073644
```
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 |