[Bug 2109823] Re: [SRU] openvswitch 3.3.4 (noble) 3.5.1 (plucky/questing) point release

[Arif Ali]

On your note Rick

I have a PPA already at [1], which I was using but without proposed
enabled.

I have now enabled proposed, and indeed get the same issue presented in
the build for questing. I have tried to reproduce this issue locally,
but that same test always passes for me, and as Bryan has highlighted,
the current package also has the same issues in questing. So, it seems
another package that openvswitch depends on (although not in the depends
list) has caused this package to fail to through the tests, which is
unfortunate. Tracking this down is now going to be painful.

On another note, I have re-built plucky in the same PPA (with proposed
enabled) this morning, and that builds ok; so I think that should be
good to go

Between me and Bryan, we'll keep investigating, and pulling the questing
build apart, and see why LP builds fail for that test, but local builds
don't

[1] https://launchpad.net/~arif-ali/+archive/ubuntu/ovs-lp2109823

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

Title:
  [SRU] openvswitch 3.3.4 (noble) 3.5.1 (plucky/questing) point release

Status in Ubuntu Cloud Archive caracal series:
  New
Status in openvswitch package in Ubuntu:
  In Progress
Status in openvswitch source package in Noble:
  Fix Committed
Status in openvswitch source package in Plucky:
  In Progress
Status in openvswitch source package in Questing:
  In Progress

Bug description:
  [Impact]
  This release sports mostly bug-fixes and we would like to make sure all of our
  supported customers have access to these improvements.

  The update contains the following package updates:

     * openvswitch 3.3.4 (noble)
     * openvswitch 3.5.1 (plucky and questing)

  For more details see:

     * https://www.openvswitch.org/releases/NEWS-3.3.4.txt
     * https://github.com/openvswitch/ovs/compare/v3.3.0...v3.3.4

     * https://www.openvswitch.org/releases/NEWS-3.5.1.txt
     * https://github.com/openvswitch/ovs/compare/v3.5.0...v3.5.1

  It will include [1], [2] and [3] which can thereby be dropped from the
  delta. This removes all the patches in debian/patches folder.

  [1]: https://github.com/openvswitch/ovs/commit/e3ed764bb246e312050416f94b1e04a1569d1a5a
  [2]: https://github.com/openvswitch/ovs/commit/c560f6ca3257dd3b64e01a4a244b02b90216858b
  [3]: https://github.com/openvswitch/ovs/commit/46af8a20ca5f5301f0679b7106948b4d96b08de7

  [Test Case]

  The following SRU process was followed:

  https://wiki.ubuntu.com/OpenStack/StableReleaseUpdates

  In order to avoid regression of existing consumers, the OpenStack team will
  run their continuous integration test against the packages that are in
  -proposed. A successful run of all available tests will be required before the
  proposed packages can be let into -updates.

  The OpenStack team will be in charge of attaching the output summary of the
  executed tests. The OpenStack team members will not mark ‘verification-done’ until
  this has happened.

  [Regression Potential]
  In order to mitigate the regression potential, the results of the
  aforementioned tests are attached to this bug.

  [other Info]
  ​​This is a regular update policy, it follows many others:
  - #1021530 [SRU] update to include stable fixes for OVS 1.4
  - #1470120 [SRU] openvswitch 2.3.2
  - #1641956 [SRU] openvswitch 2.6.1
  - #2003059 [SRU] openvswitch 3.0.3 point release
  - #2003060 [SRU] openvswitch 2.17.5 point release
  - #2025319 [SRU] openvswitch 3.1.2 point release
  - #2025323 [SRU] openvswitch 2.17.7 point release
  - #2039906 [SRU] openvswitch 3.2.1 point release
  - #2039907 [SRU] openvswitch 3.1.3 point release
  - #2039908 [SRU] openvswitch 2.17.8 point release

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