Bug 2036609

Summary: ovnkube-node pod enters CrashLoopBackOff after OVN_IMAGE is swapped
Product: OpenShift Container Platform Reporter: OpenShift BugZilla Robot <openshift-bugzilla-robot>
Component: NetworkingAssignee: Jaime CaamaƱo Ruiz <jcaamano>
Networking sub component: ovn-kubernetes QA Contact: Anurag saxena <anusaxen>
Status: CLOSED ERRATA Docs Contact:
Severity: high    
Priority: medium CC: astoycos, dcbw, ematysek, yprokule, zzhao
Version: 4.9   
Target Milestone: ---   
Target Release: 4.9.z   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: perfscale-ovn
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-04-20 14:49:50 UTC Type: ---
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: 2009404    
Bug Blocks:    

Comment 12 Eric Matysek 2022-04-13 18:50:46 UTC
@zzhao Can this bug be verified for 4.9 release?

Comment 13 zhaozhanqi 2022-04-14 06:49:14 UTC
have a test 4.9.0-0.nightly-2022-04-13-185251, after replace the OVN_IMAGE from network operator deployment many times. I did not see ovn node pod CrashLoopBackOff.  Move this bug to verified.

Comment 15 errata-xmlrpc 2022-04-20 14:49:50 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.9.29 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-2022:1363