Bug 1928157
| Summary: | 4.7 CNO claims to be done upgrading before it even starts | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Dan Winship <danw> |
| Component: | Networking | Assignee: | Dan Winship <danw> |
| Networking sub component: | openshift-sdn | QA Contact: | zhaozhanqi <zzhao> |
| Status: | CLOSED ERRATA | Docs Contact: | |
| Severity: | medium | ||
| Priority: | medium | CC: | aconstan, cdc, wking |
| Version: | 4.7 | ||
| Target Milestone: | --- | ||
| Target Release: | 4.8.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
Cause: On upgrade from 4.6 to 4.7, the network operator immediately marked itself as having fully upgraded, before it began rolling out the 4.7 versions of the openshift-sdn/ovn-kubernetes pods.
Consequence: If the network plugin upgrade fails, the cluster might mistakenly report that it had fully upgraded to 4.7 despite some nodes still running a 4.6 network plugin. (The network operator would be Degraded in this case, but it would mistakenly be reporting that it was 4.7 and Degraded, rather than 4.6 and Degraded.) Alternatively, it is possible that even if the network upgrade succeeds, the upgrade as a whole might fail due to a later step being disrupted by having the network upgrade occur at the same time.
Fix: The network operator now correctly waits for the network plugin to be upgraded to the 4.7 images before declaring itself to be upgraded.
Result: Version reporting should be correct. Upgrades should proceed in proper sequence.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2021-07-27 22:44:18 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: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1929371 | ||
|
Description
Dan Winship
2021-02-12 14:04:14 UTC
Verified this bug on 4.8.0-0.nightly-2021-02-21-102854 CNO version still old during upgrade. NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE authentication 4.8.0-0.nightly-2021-02-21-102854 True False False 38m baremetal 4.8.0-0.nightly-2021-02-21-102854 True False False 73m cloud-credential 4.8.0-0.nightly-2021-02-21-102854 True False False 75m cluster-autoscaler 4.8.0-0.nightly-2021-02-21-102854 True False False 72m config-operator 4.8.0-0.nightly-2021-02-21-102854 True False False 73m console 4.8.0-0.nightly-2021-02-21-102854 True False False 8m43s csi-snapshot-controller 4.8.0-0.nightly-2021-02-21-102854 True False False 47m dns 4.7.0-rc.3 True False False 71m etcd 4.8.0-0.nightly-2021-02-21-102854 True False False 71m image-registry 4.8.0-0.nightly-2021-02-21-102854 True False False 47m ingress 4.8.0-0.nightly-2021-02-21-102854 True False False 62m insights 4.8.0-0.nightly-2021-02-21-102854 True False False 66m kube-apiserver 4.8.0-0.nightly-2021-02-21-102854 True False False 70m kube-controller-manager 4.8.0-0.nightly-2021-02-21-102854 True False False 71m kube-scheduler 4.8.0-0.nightly-2021-02-21-102854 True False False 70m kube-storage-version-migrator 4.8.0-0.nightly-2021-02-21-102854 True False False 47m machine-api 4.8.0-0.nightly-2021-02-21-102854 True False False 63m machine-approver 4.8.0-0.nightly-2021-02-21-102854 True False False 72m machine-config 4.7.0-rc.3 True False False 71m marketplace 4.8.0-0.nightly-2021-02-21-102854 True False False 8m56s monitoring 4.8.0-0.nightly-2021-02-21-102854 True False False 60m network 4.7.0-rc.3 True True False 73m node-tuning 4.8.0-0.nightly-2021-02-21-102854 True False False 9m13s openshift-apiserver 4.8.0-0.nightly-2021-02-21-102854 True False False 66m openshift-controller-manager 4.8.0-0.nightly-2021-02-21-102854 True False False 65m openshift-samples 4.8.0-0.nightly-2021-02-21-102854 True False False 9m22s operator-lifecycle-manager 4.8.0-0.nightly-2021-02-21-102854 True False False 72m operator-lifecycle-manager-catalog 4.8.0-0.nightly-2021-02-21-102854 True False False 72m operator-lifecycle-manager-packageserver 4.8.0-0.nightly-2021-02-21-102854 True False False 9m9s service-ca 4.8.0-0.nightly-2021-02-21-102854 True False False 73m storage 4.8.0-0.nightly-2021-02-21-102854 True False False 46m 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 (Moderate: OpenShift Container Platform 4.8.2 bug fix and security update), 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/RHSA-2021:2438 |