Bug 1929371

Summary: 4.7 CNO claims to be done upgrading before it even starts
Product: OpenShift Container Platform Reporter: OpenShift BugZilla Robot <openshift-bugzilla-robot>
Component: NetworkingAssignee: Dan Winship <danw>
Networking sub component: openshift-sdn QA Contact: zhaozhanqi <zzhao>
Status: CLOSED ERRATA Docs Contact:
Severity: medium    
Priority: medium CC: aconstan, anbhat, bbennett, cdc, wking
Version: 4.7   
Target Milestone: ---   
Target Release: 4.7.z   
Hardware: Unspecified   
OS: Unspecified   
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-03-30 04:46:29 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On: 1928157    
Bug Blocks:    

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.