Bug 1845702

Summary: Update openvswitch2.13 to -29 or later
Product: OpenShift Container Platform Reporter: Dan Williams <dcbw>
Component: NetworkingAssignee: Ben Bennett <bbennett>
Networking sub component: ovn-kubernetes QA Contact: zhaozhanqi <zzhao>
Status: CLOSED ERRATA Docs Contact:
Severity: urgent    
Priority: urgent CC: anusaxen
Version: 4.5   
Target Milestone: ---   
Target Release: 4.6.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1845705 (view as bug list) Environment:
Last Closed: 2020-10-27 16:06:02 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:
Bug Depends On:    
Bug Blocks: 1845705    

Comment 3 Anurag saxena 2020-06-15 18:14:32 UTC
Openvswitch rpms seems now pointing to 2.13.0-30 on 4.6.0-0.nightly-2020-06-15-145117

$ oc get clusterversion
NAME      VERSION                             AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.6.0-0.nightly-2020-06-15-145117   True        False         10m     Cluster version is 4.6.0-0.nightly-2020-06-15-145117
$ oc rsh ovnkube-node-2rsp9
Defaulting container name to ovn-controller.
Use 'oc describe pod/ovnkube-node-2rsp9 -n openshift-ovn-kubernetes' to see all of the containers in this pod.

sh-4.2# rpm -qa | grep -i openv
openvswitch-selinux-extra-policy-1.0-15.el7fdp.noarch
openvswitch2.13-2.13.0-30.el7fdp.x86_64
openvswitch2.13-devel-2.13.0-30.el7fdp.x86_64

sh-4.2# ovs-vsctl --version
ovs-vsctl (Open vSwitch) 2.13.0

Comment 5 errata-xmlrpc 2020-10-27 16:06:02 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 (OpenShift Container Platform 4.6 GA Images), 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/RHBA-2020:4196