Description of problem: In 4.7 there is no reason to have the OVS pod. Version-Release number of selected component (if applicable): 4.7 How reproducible: always Steps to Reproduce: 1. oc get ds ovs -n openshift-sdn Actual results: There is an ovs daemonset Expected results: There is no ovs daemonset Additional info:
*** Bug 1934782 has been marked as a duplicate of this bug. ***
Hello, Could you please share with us any new updates ? Thanks in advance.
Verified this bug on 4.8.0-0.nightly-2021-04-28-005607 with openshift-sdn and ovn cluster And daemonset ovs already be removed $ oc get ds -n openshift-ovn-kubernetes NAME DESIRED CURRENT READY UP-TO-DATE AVAILABLE NODE SELECTOR AGE ovnkube-master 3 3 3 3 3 beta.kubernetes.io/os=linux,node-role.kubernetes.io/master= 5h23m ovnkube-node 6 6 6 6 6 beta.kubernetes.io/os=linux 5h23m and must-gather already collect the related logs: crio_service.log machine-config-daemon-firstboot_service.log NetworkManager_service.log ovs-configuration_service.log ovs-vswitchd_service.log kubelet_service.log machine-config-daemon-host_service.log openvswitch_service.log ovsdb-server_service.log
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.8.2 bug fix and 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. https://access.redhat.com/errata/RHSA-2021:2438