Ubuntu Cloud Archive

Comment 0 for bug 2032770

Revision history for this message

Mustafa Kemal Gilor (mustafakemalgilor) wrote on 2023-08-23: [OVN] port creation with --enable-uplink-status-propagation does not work with OVN mechanism driver

The port "uplink_status_propagation" feature does not work when OVN is used as the mechanism driver. The reproducer below is working fine with openvswitch as the mechanism driver, but not with the OVN:

openstack port create --binding-profile trusted=true --enable-uplink-status-propagation --net private --vnic-type direct test-sriov-bond-enable-uplink-status-propagation-vm-1-port-1

The command fails with the following error when OVN is the mech driver:

BadRequestException: 400: Client Error for url: https://10.5.3.81:9696/v2.0/ports, Unrecognized attribute(s) 'propagate_uplink_status'

With ML2/OVS, the port creation command above succeeds without any errors.

As for the ml2_conf, "uplink_status_propagation" is listed in the extension drivers:

[ml2]
extension_drivers=port_security,dns_domain_ports,uplink_status_propagation
type_drivers = geneve,gre,vlan,flat,local
tenant_network_types = geneve,gre,vlan,flat,local
mechanism_drivers = ovn,sriovnicswitch
/*...*/

I also found the following document which shows the feature gap between ML2/OVS and OVN, but the uplink_status_propagation is not listed: https://docs.openstack.org/neutron/latest/ovn/gaps.html#id9 , maybe this page can be updated as well.