[SRU] OVN 22.03.2 point release
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu Cloud Archive |
Invalid
|
Undecided
|
Unassigned | ||
Ovn-22.03 |
Fix Released
|
High
|
Unassigned | ||
Yoga |
Fix Released
|
Undecided
|
Unassigned | ||
ovn (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Jammy |
Fix Released
|
High
|
Unassigned |
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:
* ovn 22.03.2
[Test Case]
The following SRU process was followed:
https:/
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.
Changed in ovn (Ubuntu): | |
status: | New → Invalid |
Changed in ovn (Ubuntu Jammy): | |
importance: | Undecided → High |
Changed in ovn (Ubuntu Jammy): | |
status: | New → Triaged |
Changed in cloud-archive: | |
status: | New → Invalid |
tags: |
added: verification-ovn-22.03-done removed: verification-ovn-22.03-needed |
Some background on the addition of flaky tests in the SRU package:
There are unfortunately a number of tests in the OVN testsuite that have timing issues and as a consequence appear as flaky when run under load in the Debian and Ubuntu build farms. The upstream is currently working through these issues, but it is a sizable undertaking, which will still take some time to fully fix.
We go through lengths to identify the underlying issue whenever a new test starts to fail, which can be observed in a recent bash regression which was caught by us [0].
The listed tests are passing when run on an unloaded system from the Debian/Ubuntu package sources, so there is no doubt that the functionality is intact in our composition of bits. For completeness I have included the output of a successful test run with the affected tests [1].
We regularly disable tests for the same reasons in Debian unstable with bug references [2][3][4][5][6][7], and I unfortunately did not go through the same rigor in tying these listings in the stable backport, for which I apologize.
0: https:/ /bugs.launchpad .net/bugs/ 1997093 /pastebin. ubuntu. com/p/R3RHfNcR7 K/ /salsa. debian. org/openstack- team/third- party/ovn/ -/commit/ 923f0b1a3a4ade0 a367a3be6db30f6 b57acafe7e /salsa. debian. org/openstack- team/third- party/ovn/ -/commit/ cc2a217dc775cc6 0f704a13f85e6ec 07933902e3 /bugs.launchpad .net/bugs/ 2002406 /bugs.launchpad .net/bugs/ 2002475 /bugs.launchpad .net/bugs/ 2002476 /bugs.launchpad .net/bugs/ 2002477
1: https:/
2: https:/
3: https:/
4: https:/
5: https:/
6: https:/
7: https:/