This bug was fixed in the package openvswitch - 3.3.0-1ubuntu3
---
openvswitch (3.3.0-1ubuntu3) noble; urgency=medium
* d/p/ofproto-dpif-xlate-Fix-continuations-with-associated-
metering.patch: Cherry-pick fix required for OVN 24.03.2
(LP: #2066906).
openvswitch (3.3.0-1ubu
Build logs do indeed contain a passing `ofproto-dpif - continuation with
meters` test.
OVN 24.03.2 successfully built:
https://launchpad.net/ubuntu/+source/ovn/24.03.2-0ubuntu0.24.04.1
And has passing autopkgtests:
https://autopkgtest.ubuntu.com/results/autopkgtest-noble/noble/amd64/o/ovn/2024060
Hello, Mauricio,
Thank you for your thorough review.
The version was chosen knowing that there is a higher order version
already present in Oracular and that a point release update will
eventually be SRU'ed using the full `0.24.04.1` suffix, I could still
have used the micro version as you propos
FTR; the autopkgtest results have been reviewed/triaged and as a result
re-runs have been requested.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2066906
Title:
[noble] Missing fix for continuation
Review feedback:
- Versioning:
It's standard practice that version string for stable releases are
incremented by `ubuntu0.1`, and development release, by `ubuntu1`
(please see [1]).
This SRU/upload incremented by `ubuntu1`, but this was accepted
previously (noble: ubuntu1, noble-proposed: ubuntu
Added to the 'Regression Potential' an statement along the lines of the
intended meaning 'Where problems could occur' [3], which relates to
where/what the patch changes.
Please amend/correct in case I missed something/misunderstood the patch;
thanks!
[3] https://wiki.ubuntu.com/StableReleaseUpdat
Marking devel/oracular as Fix Released (patch included):
$ pull-lp-source openvswitch
Found openvswitch 3.3.0-5 in oracular
...
$ cd openvswitch-3.3.0
$ grep 'ofproto-dpif - continuation with meters' tests/ofproto-dpif.at
AT_SETUP([ofproto-dpif - continuation with meters])
$ grep -A6 '^put_contr
This is arguably a reasonable combination (although with slight differences)
of 'FTBFS' and 'Autopkgtest failures' (i.e., 'for successful build/test run')
acceptable per SRU policy (included below), thus should not need staging.
And even though this SRU (openvswitch) is directed at fixing/preventi
Clarified/added '(Bug 2066908: [SRU] ovn 24.03.2 point release)' in the
Impact section.
** Description changed:
[ Impact ]
There is a bug in Open vSwitch which is required for successful build and
test run for OVN 24.03.2.
+ (Bug 2066908: [SRU] ovn 24.03.2 point release)
[ Test plan ]
