Bug 1929371 - 4.7 CNO claims to be done upgrading before it even starts
Summary: 4.7 CNO claims to be done upgrading before it even starts
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 4.7
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.7.z
Assignee: Dan Winship
QA Contact: zhaozhanqi
Depends On: 1928157
TreeView+ depends on / blocked
Reported: 2021-02-16 18:29 UTC by OpenShift BugZilla Robot
Modified: 2021-03-30 04:47 UTC (History)
5 users (show)

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.
Clone Of:
Last Closed: 2021-03-30 04:46:29 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift cluster-network-operator pull 983 0 None open [release-4.7] Bug 1929371: Don't set ClusterOperator Version until rollout is complete 2021-02-16 18:30:02 UTC
Red Hat Product Errata RHSA-2021:0957 0 None None None 2021-03-30 04:47:52 UTC

Comment 2 zhaozhanqi 2021-03-22 06:10:34 UTC
Verified this bug on 4.7.0-0.nightly-2021-03-22-025559

Comment 5 errata-xmlrpc 2021-03-30 04:46:29 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 (Moderate: OpenShift Container Platform 4.7.4 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.


Note You need to log in before you can comment on or make changes to this bug.