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

[Mustafa Kemal Gilor]

** Description changed:

- 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:
+ [Impact]
  
- 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
+ This SRU is a backport of
+ https://review.opendev.org/c/openstack/neutron/+/892895 to the
+ respective Ubuntu and UCA releases. The patch is merged to all
+ respective upstream branches (master & stable/[u,v,w,x,y,z,2023.1(a)]).
  
- The command fails with the following error when OVN is the mech driver:
+ This SRU intends to add the missing 'uplink-status-propagation'
+ extension to ML2/OVN. This extension is already present and working in
+ ML2/OVS, and it is supported by ML2/OVN but the extension is somehow not
+ added to ML2/OVN. The patch simply adds the missing extension to the
+ ML2/OVN too.
  
- BadRequestException: 400: Client Error for url:
- https://10.5.3.81:9696/v2.0/ports, Unrecognized attribute(s)
+ The impact of this is visible for the deployments migrating from ML2/OVS
+ to ML2/OVN. The following command fails to work on ML2/OVN:
+ 
+ ```
+ openstack port create --network 8d30fb08-2c6a-42fd-98c4-223d345c8c4f --binding-profile trusted=true --enable-uplink-status-propagation --vnic-type direct aaa
+ 
+ # BadRequestException: 400: Client Error for url:
+ https://mycloud.example.com: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:
+ The fix corrects this behavior by adding the missing extension.
  
- [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
- /*...*/
+ [Test Case]
  
- 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.
+ - Deploy a Focal/Yoga cloud:
+     - ./generate-bundle.sh -s focal -r yoga --name test-focal-yoga-stack --run --ovn
+     # After the dust settles
+     - ./configure
+     - source ./novarc
+ - openstack port create --network <network-id> --binding-profile trusted=true --enable-uplink-status-propagation --vnic-type direct aaa
+ - It should fail with "BadRequestException: 400: Client Error for url: https://mycloud.example.com:9696/v2.0/ports, Unrecognized attribute(s) 'propagate_uplink_status'"
+ 
+ To confirm the fix, repeat the scenario and observe that the error
+ disappears and port creation succeeds.
+ 
+ [Regression Potential]
+ The patch is quite trivial and should not affect any deployment negatively. The extension is optional and disabled by default.

** Summary changed:

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

** Patch added: "focal.debdiff"
   https://bugs.launchpad.net/neutron/+bug/2032770/+attachment/5715216/+files/focal.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
OpenStack, which is subscribed to Ubuntu Cloud Archive.
https://bugs.launchpad.net/bugs/2032770

Title:
  [SRU] [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:
  [Impact]

  This SRU is a backport of
  https://review.opendev.org/c/openstack/neutron/+/892895 to the
  respective Ubuntu and UCA releases. The patch is merged to all
  respective upstream branches (master &
  stable/[u,v,w,x,y,z,2023.1(a)]).

  This SRU intends to add the missing 'uplink-status-propagation'
  extension to ML2/OVN. This extension is already present and working in
  ML2/OVS, and it is supported by ML2/OVN but the extension is somehow
  not added to ML2/OVN. The patch simply adds the missing extension to
  the ML2/OVN too.

  The impact of this is visible for the deployments migrating from
  ML2/OVS to ML2/OVN. The following command fails to work on ML2/OVN:

  ```
  openstack port create --network 8d30fb08-2c6a-42fd-98c4-223d345c8c4f --binding-profile trusted=true --enable-uplink-status-propagation --vnic-type direct aaa

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

  ```

  The fix corrects this behavior by adding the missing extension.

  [Test Case]

  - Deploy a Focal/Yoga cloud:
      - ./generate-bundle.sh -s focal -r yoga --name test-focal-yoga-stack --run --ovn
      # After the dust settles
      - ./configure
      - source ./novarc
  - openstack port create --network <network-id> --binding-profile trusted=true --enable-uplink-status-propagation --vnic-type direct aaa
  - It should fail with "BadRequestException: 400: Client Error for url: https://mycloud.example.com:9696/v2.0/ports, Unrecognized attribute(s) 'propagate_uplink_status'"

  To confirm the fix, repeat the scenario and observe that the error
  disappears and port creation succeeds.

  [Regression Potential]
  The patch is quite trivial and should not affect any deployment negatively. The extension is optional and disabled by default.

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