RHV 4.4 is using OVN/OVS 2.11, which is old version and there won't be added any new features into it. So the only way forward is to upgrade to OVN/OVS 2.13+, which will allow us to use new features (for example ipsec as requested in BZ1782056) and allow also future upgrades (OVN/OVS 2.13+ provides functionality to work with older versions, for example OVN/OVS 2.15 should work with OVN/OVS 2.13). But there are consequences: 1. According to OVN team running OVN/OVS 2.13 with OVN/OVS 2.11 is unsupported -> we would need to change our OVN support to exclude 4.3 hosts. 2. Even though OVN/OVS 2.13 and 2.11 is unsupported, we still need to provide some reasonable upgrade path - we need to check if upgrade of hosts still using OVN/OVS 2.11 in a cluster still can finish successfully (those hosts can be upgraded to OVN/OVS 2.13) after OVN/OVS is upgraded to 2.13 on RHV Manager This is RFE is just preliminary, it's not yet acked until we verify that our tests don't detect any failure during upgrade. And of course we will need to determine which version we want to upgrade to: 2.13 or 2.15
This RFE has failedQA, as the ovn-sb is keeping the chassis in inconsistent state. The Chassis IDs are UUID instead of hostname. This preventing the VMs running on different hosts, to fail to communicate with each other after the hosts upgraded to ovn/ovs 2.15 We probably need to delete the chassis during the host upgrade/installation and let the ovn-controller to add itself again. Moving back to ASSIGNED for further work. Tested with: rhvm-4.5.0-0.237.el8ev.noarch ovirt-provider-ovn-1.2.35-1.el8ev.noarch ovn-2021-21.12.0-32.el8fdp.x86_64 openvswitch2.15-2.15.0-84.el8fdp.x86_64 vdsm-4.50.0.10-1.el8ev.x86_64 ovirt-openvswitch-2.15-3.el8ev.noarch
We are past 4.5.0 feature freeze, please re-target.
Updated doctext according to https://github.com/oVirt/ovirt-site/pull/2821/files/87730ec701d42d1be8142fc1e64b4d229c566c3f#r839547966
Verified on - rhvm-4.5.0.2-0.7.el8ev.noarch with the next packages: ovirt-provider-ovn-1.2.36-1.el8ev.noarch ovn-2021-21.12.0-45.el8fdp.x86_64 ovn-2021-central-21.12.0-45.el8fdp.x86_64 ovirt-openvswitch-2.15-3.el8ev.noarch ovirt-openvswitch-ovn-central-2.15-3.el8ev.noarch ovirt-openvswitch-ovn-2.15-3.el8ev.noarch ovirt-openvswitch-ovn-common-2.15-3.el8ev.noarch openvswitch2.15-2.15.0-94.el8fdp.x86_64 ovirt-python-openvswitch-2.15-3.el8ev.noarch ovirt-openvswitch-ovn-host-2.15-3.el8ev.noarch python3-openvswitch2.15-2.15.0-94.el8fdp.x86_64 ovn-2021-21.12.0-45.el8fdp.x86_64 ovn-2021-host-21.12.0-45.el8fdp.x86_64 ovirt-provider-ovn-driver-1.2.36-1.el8ev.noarch vdsm-4.50.0.12-1.el8ev.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 (Moderate: RHV Engine and Host Common Packages 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-2022:4712