Bug 1843948

Summary:	[Network operator] Upgrade from 2.3 to 2.4 - Network operator fails to upgrade ovs-cni pods, upgrade is not completed
Product:	Container Native Virtualization (CNV)	Reporter:	Ruth Netser <rnetser>
Component:	Networking	Assignee:	Petr Horáček <phoracek>
Status:	CLOSED ERRATA	QA Contact:	Ruth Netser <rnetser>
Severity:	urgent	Docs Contact:
Priority:	urgent
Version:	2.4.0	CC:	cnv-qe-bugs, ncredi
Target Milestone:	---
Target Release:	2.4.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	cluster-network-addons-operator-container-v2.4.0-26	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-07-28 19:10:31 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 2020-06-04 14:55:58 UTC

Thanks for the detailed report. This is what the init container fails with:

[cnv-qe-jenkins@cnv-executor-ruty23-1 ~]$ oc -n openshift-cnv logs ovs-cni-amd64-rfpgm -c ovs-cni-plugin -p
cp: cannot stat '/ovs': No such file or directory

Other pods that were not failing seem to be from previous installation.

I will post the fix in a moment.

Comment 2 Petr Horáček 2020-06-04 19:02:30 UTC

This should be fixed in the next build.

Comment 3 Ruth Netser 2020-06-09 09:14:54 UTC

Verified upgrade 2.3.0 -> 2.4.0 with ovs-cni-plugin-container-v2.4.0-25
All ovs-cni pods were upgraded and are running.

Comment 6 errata-xmlrpc 2020-07-28 19:10:31 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/RHSA-2020:3194