Description of problem: Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Check this issue on payload 4.4.0-0.nightly-2020-02-09-220310 The ovn is still ovn2.11 rpm -qa | grep -i ovn ovn2.11-central-2.11.1-24.el7fdp.x86_64 ovn2.11-vtep-2.11.1-24.el7fdp.x86_64 ovn2.11-2.11.1-24.el7fdp.x86_64 ovn2.11-host-2.11.1-24.el7fdp.x86_64 the ovs is using 2.12 rpm -qa | grep -i openvswitch openvswitch2.12-2.12.0-12.el7fdp.x86_64 openvswitch-selinux-extra-policy-1.0-14.el7fdp.noarch openvswitch2.12-devel-2.12.0-12.el7fdp.x86_64
*** Bug 1798191 has been marked as a duplicate of this bug. ***
Tested and verified in 4.4.0-0.nightly-2020-03-03-065638 [root@dhcp-41-193 FILE]# oc rsh pod/ovnkube-master-69q68 Defaulting container name to northd. Use 'oc describe pod/ovnkube-master-69q68 -n openshift-ovn-kubernetes' to see all of the containers in this pod. sh-4.2# rpm -qa | grep -i ovn ovn2.12-2.12.0-32.el7fdn.x86_64 ovn2.12-vtep-2.12.0-32.el7fdn.x86_64 ovn2.12-central-2.12.0-32.el7fdn.x86_64 ovn2.12-host-2.12.0-32.el7fdn.x86_64 sh-4.2# rpm -qa | grep -i openvswitch openvswitch2.12-2.12.0-21.el7fdn.x86_64 openvswitch-selinux-extra-policy-1.0-14.el7fdp.noarch openvswitch2.12-devel-2.12.0-21.el7fdn.x86_64 sh-4.2# exit exit [root@dhcp-41-193 FILE]# oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.4.0-0.nightly-2020-03-03-065638 True False 4h35m Cluster version is 4.4.0-0.nightly-2020-03-03-065638
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/RHBA-2020:0581