Description of problem: we need to cover the scenario test on migration sriov from ml2ovs to ovn based on this deployment : [New Test] SR-IOV from OSP 13 to OSP 16 with single VM with 2 interfaces 1.VM1 has SR-IOV VF with VLAN provider networks and L2 agent for DHCP services ( nor routing) 2.VM1 has OVS with VLAN provider networks and L2 Agent for DHCP/metadata services (no routing) 3.Migrate to OVN for SR-IOV this SR-IOV scenario Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Migration to ML2OVN on SRIOV environment tested on RHOS-16.1-RHEL-8-20200903.n.0 and worked using the following guidelines(in addition to usual OVN migration instructions from the official documentation): 1. Add OS::TripleO::Services::OVNMetadataAgent to Controller role. 2. Copy overcloud_deploy.sh to overcloud-deploy-ovn.sh 3. Delete ML2OVS-specific templates from overcloud-deploy-ovn.sh 4. Add the following OVN-specific templates to the end of the overcloud deploy command: -e /usr/share/openstack-tripleo-heat-templates/environments/services/neutron-ovn-ha.yaml \ -e /usr/share/openstack-tripleo-heat-templates/environments/services/neutron-ovn-sriov.yaml \ -e /home/stack/ovn-extras.yaml Tested with workload using normal and direct (vf) ports. With direct-physical (PF port) we are blocked with this issue: Bug 1879546 - [OSP16.1]Migration from ML2OVS to ML2OVN fails in case some SRIOV PF/VF ports are in use
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 (Red Hat OpenStack Platform 16.1 bug fix and enhancement 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/RHEA-2020:4284