Bug 1778446

Summary: ovs-cni in CrashLoopBackOff
Product: Container Native Virtualization (CNV) Reporter: Yossi Segev <ysegev>
Component: NetworkingAssignee: Petr Horáček <phoracek>
Status: CLOSED ERRATA QA Contact: Meni Yakove <myakove>
Severity: high Docs Contact:
Priority: high    
Version: 2.2.0CC: atragler, cnv-qe-bugs, ellorent, myakove, ncredi
Target Milestone: ---   
Target Release: 2.2.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: cluster-network-addons-operator-container-v2.2.0-6 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-01-30 16:27:33 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:

Comment 1 Petr Horáček 2019-12-01 09:10:23 UTC
This is caused by a mismatch in OVS-CNI and CNAO versions D/S. I'm pushing a proper CNAO D/S now.

Comment 2 Yossi Segev 2019-12-02 07:36:05 UTC
ovs-cni seems stable after installing a newer CNV version, where CNAO version is now v2.2.0-6 (ovs-cni-plugin & -marker version is still v2.2.0-3).

Comment 4 errata-xmlrpc 2020-01-30 16:27:33 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, 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/RHEA-2020:0307