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

Tue Jul 22 18:23:53 UTC 2025

Hello,

I've been doing some testing on this and first tried a no-change rebuild
of 3.5.0-1build1 on questing proposed. This can be seen in the PPA here:
https://launchpad.net/~bryanfraschetti/+archive/ubuntu/ovs-
proposed/+packages

Looking at the build log on amd64, s390x, and arm64, 3.5.0 is now
failing in a similar way to 3.5.1 (on OVS datapath actions parsing and
formatting - userdata overflow FAILED (odp.at:468) with some additional
failures). Here's the build log on amd64:
https://launchpadlibrarian.net/806517147/buildlog_ubuntu-questing-
amd64.openvswitch_3.5.0-1build2_BUILDING.txt.gz. So a previously
successfully built package is now failing on -proposed.

It seemed like the problem is not with the package but maybe with one of
it's dependencies that's in -proposed causing the breakage. I decided to
check locally to try and isolate which package in -proposed was causing
the failure.

To test locally I
- created a VM from the daily amd64 questing iso: http://www.cdimage.ubuntu.com/daily-live/current
- enabled proposed
- pinned questing-proposed to high priority
Package: *
Pin: release a=questing-proposed
Pin-Priority: 1001
- apt source openvswitch, which pulled in 3.5.1
- debuild -us -uc

Which succeeded with minor bashcomp failures

I created a script to compare the package versions from the CI with the
installed versions on my system and found that there were no meaningful
differences. See the differences below. "NOT INSTALLED" means the
package was present in the CI but not locally. Similarly, "CI" indicates
what was in the CI while Installed indicates what's on my VM. The
differences are because I'm running this locally a few days later than
when the CI runner executed.

NOT INSTALLED: libapt-pkg6.0t64 (proposed: 2.9.27ubuntu1)
MISMATCH: libreadline8t64
  CI : 8.2-6
  Installed: 8.3-1
MISMATCH: libxml2-16
  CI : 2.14.4+dfsg-0exp1
  Installed: 2.14.5+dfsg-0exp1
MISMATCH: readline-common
  CI : 8.2-6
  Installed: 8.3-1
MISMATCH: rust-coreutils
  CI : 0.1.0-0ubuntu1
  Installed: 0.1.0+git20250711.2ba3a33-0ubuntu1
NOT INSTALLED: sbuild-build-depends-main-dummy (proposed: 0.invalid.0)

I noticed that my VM was using the 6.15 kernel, while the CI was using
6.8.0-63 #66, so I downgraded the kernel and built again. This succeeded
as well and there was no difference compared to the 6.15 kernel (see
attached build log).

Since it doesn't seem to be the package, the dependencies, the system package versions in -updates or -proposed, or the kernel, I'm not sure what could be causing the CI failure. Maybe it's a problem with the base image or some LP-specific customizations to the build environment if there are any? The following are just things I'm curious about
- Where LP pulls the image (if I can pull this image maybe I can reproduce the failure locally)
- In what ways it differs from the questing isos
- How often is it updated (maybe a newer base image will solve the failure)

To summarize:
Rebuilding 3.5.0 (the ovs which was released on questing) in the LP CI against -proposed fails in a similar way to 3.5.1
Building 3.5.1 succeeds on the current questing server iso even with -proposed enabled.

** Attachment added: "openvswitch_3.5.1-0ubuntu1_amd64.build"
   https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/2109823/+attachment/5892285/+files/openvswitch_3.5.1-0ubuntu1_amd64.build

-- 
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