+++ This bug was initially created as a clone of Bug #1882693 +++ Description of problem: We need to pin the OVS version on 4.4 to the version running on the latest release: 4.4.0-0.nightly-2020-09-24-222539 openvswitch2.13-2.13.0-46.el7fdp.x86_64 Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
4.5.0-0.nightly-2020-09-24-094317 is running; openvswitch2.13-2.13.0-46.el7fdp.x86_64
What is the plan here? We need to get the pin in in case we get surprised by an update...
On release registry.ci.openshift.org/ocp/release:4.5.0-0.nightly-2021-02-04-091104: > oc exec ovnkube-node-dv54n -c ovnkube-node -- yum list | grep openv openvswitch-selinux-extra-policy.noarch openvswitch2.13.x86_64 2.13.0-62.el7fdp @rhel-fast-datapath-rpms-x86_64 openvswitch2.13-devel.x86_64 2.13.0-62.el7fdp @rhel-fast-datapath-rpms-x86_64
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 (Important: OpenShift Container Platform 4.5.31 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:0313
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 500 days