← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 2032770] Re: [OVN] port creation with --enable-uplink-status-propagation does not work with OVN mechanism driver

 

** Also affects: cloud-archive/victoria
   Importance: Undecided
       Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/2032770

Title:
  [OVN] port creation with --enable-uplink-status-propagation does not
  work with OVN mechanism driver

Status in Ubuntu Cloud Archive:
  New
Status in Ubuntu Cloud Archive antelope series:
  New
Status in Ubuntu Cloud Archive ussuri series:
  Fix Committed
Status in Ubuntu Cloud Archive victoria series:
  New
Status in Ubuntu Cloud Archive wallaby series:
  New
Status in Ubuntu Cloud Archive xena series:
  New
Status in Ubuntu Cloud Archive yoga series:
  New
Status in Ubuntu Cloud Archive zed series:
  New
Status in neutron:
  Fix Released
Status in neutron package in Ubuntu:
  New
Status in neutron source package in Focal:
  New
Status in neutron source package in Jammy:
  New
Status in neutron source package in Lunar:
  New

Bug description:
  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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/2032770/+subscriptions