yahoo-eng-team team mailing list archive

[James Page <2032770@xxxxxxxxxxxxxxxxxx>]

This bug was fixed in the package neutron - 2:16.4.2-0ubuntu6.4~cloud0
---------------

 neutron (2:16.4.2-0ubuntu6.4~cloud0) bionic-ussuri; urgency=medium
 .
   * New update for the Ubuntu Cloud Archive.
 .
 neutron (2:16.4.2-0ubuntu6.4) focal; urgency=medium
 .
   [ Corey Bryant ]
   * d/p/ovn-db-sync-continue-on-duplicate-normalise.patch: Cherry-picked
     from upstream to allow ovn_db_sync to continue on duplicate normalised
     CIDR (LP: #1961112).
   * d/p/ovn-db-sync-check-for-router-port-differences.patch:
     Cherry-picked from upstream to ensure router ports are marked
     for needing updates only if they have changed (LP: #2030773).
   * d/p/ovn-specify-port-type-if-router-port-when-updating.patch:
     Specify port type if it's a router port when updating to avoid
     port flapping (LP: #1955578).
   * d/p/fix-acl-sync-when-default-sg-group-created.patch:
     Cherry-picked form upstream to fix ACL sync when default security
     group is created (LP: #2008943).
 .
   [ Mustafa Kemal GILOR ]
   * d/p/add_uplink_status_propagation.patch: Add the
     'uplink-status-propagation' extension to ML2/OVN (LP: #2032770).


** Changed in: cloud-archive/ussuri
       Status: Fix Committed => Fix Released

-- 
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:
  [SRU] [OVN] port creation with --enable-uplink-status-propagation does
  not work with OVN mechanism driver

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

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