Description of problem:
While swapping the OVN_IMAGE one of the ovnkube pods enters a CrashLoopBackOff state
Version-Release number of selected component (if applicable):
Not Always, about once every five installs
This can be resolved by running systemctl restart ovs-configuration on the node
@msheth: What were the images that we used? (the old one and the new one?)
I checked this bz with nightly version 4.10.0-0.nightly-2021-11-15-034648 and tried to update OVN_IMAGE in CNO several times but I didn't encounter any pods entering in CrashLoopBackOff state.
Marking this verified.
*** Bug 2028629 has been marked as a duplicate of this bug. ***
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.10.3 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.
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 500 days