[Bug 1920141] Re: [SRU] openvswitch 2.13.3 / linking changes in DPDK 19.11.x

Wed Mar 24 07:57:54 UTC 2021

This was reviewed and tested by Jamespage (in regard to the OVS  build) and by upstream (in regard to the changes on top of 19.11.7 and for the stable release itself).
Thereby I think this is ready to enter the SRU process.

Uploaded to F/G-unapproved
- dpdk_19.11.7-0ubuntu0.20.04.1_source.changes
- dpdk_19.11.7-0ubuntu0.20.10.1_source.changes

** Description changed:

+ --- SRU-OVS ---
+ 
  [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 2.13.3

  [Test Case]
  The following SRU process was followed:
  https://wiki.ubuntu.com/OpenStackUpdates

  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.

- >> Related DPDK fix <<<
+ 
+ --- SRU DPDK for this bug ---
+ 
  [Impact]
- Due to changes landed in error in the 19.11 stable DPDK branch linking of OVS with DPDK is currently broken in Focal and Groovy.
+ 
+ Due to changes landed in error in the 19.11 stable DPDK branch linking
+ of OVS with DPDK is currently broken in Focal and Groovy.
+ 
+ See http://mails.dpdk.org/archives/stable/2021-March/029418.html

  [Test Case]
+ 
  No change rebuild of the openvswitch package

  [Regression Potential]
- The offending commits should not have landed into the stable DPDK branch upstream; this has been discussed with developers involved with this change and it was agreed that they will be reverted.
+ 
+ The offending commits should not have landed into the stable DPDK branch
+ upstream; this has been discussed with developers involved with this
+ change and it was agreed that they will be reverted.
+ 
+ In theory one could say that the linking "now changes from 19.11.6" and
+ that is correct. But that is an update-regression, not long in the archive
+ and broke the primary in-archive-user being OVS. Therefore the benefit of reverting this outweighs this particular regression.
+ 
+ 
+ --- SRU DPDK for the general MRE ---
+ 
+ This bug tracks an update for the DPDK packages in:
+ - Focal 19.11.6 -> 19.11.7
+ - Groovy 19.11.6 -> 19.11.7
+ 
+ Ready as of March 2021.
+ 
+ 17.11.x (Bionic) is no more getting such releases by upstream and 20.11
+ (Hirsute) is new and up to date (20.11.1 will come to Hirsute in ~a
+ month).
+ 
+ This update includes bugfixes only following the SRU policy exception
+ defined at https://wiki.ubuntu.com/StableReleaseUpdates/DPDK.
+ 
+ No new features added, a classic stable release with a bunch of fixes
+ aggregated and enhanced testing by the companies being part of the DPDK
+ community.
+ 
+ [Impact]
+ 
+ Stable release update so not directly applicable; see the exception policy document linked above.
+ For Reference - former cases are here:
+ - https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1784816
+ - https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1817675
+ - https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1836365
+ - https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1912464
+ 
+ [Major Changes]
+ 
+ As listed by upstream all is supposed to be fixes, no features:
+ https://doc.dpdk.org/guides-19.11/rel_notes/release_19_11.html#id18
+ 
+ [Test Plan]
+ 
+ See https://wiki.ubuntu.com/StableReleaseUpdates/DPDK#SRU_TestVerify
+ I'll attach a log of executing said tests from a ppa with the upload
+ and explain why if there are any non passing tests.
+ 
+ [Regression Potential]
+ 
+ Upstream performs extensive testing before release, giving us a high
+ degree of confidence in the general case. There problems are most likely
+ to manifest in Ubuntu-specific integrations, such as in relation to the
+ versions of dependencies available and other packaging-specific matters.

** Changed in: dpdk (Ubuntu Focal)
     Assignee: (unassigned) => Christian Ehrhardt  (paelzer)

** Changed in: dpdk (Ubuntu Groovy)
     Assignee: (unassigned) => Christian Ehrhardt  (paelzer)

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

Title:
  [SRU] openvswitch 2.13.3 / linking changes in DPDK 19.11.x

Status in dpdk package in Ubuntu:
  Fix Released
Status in openvswitch package in Ubuntu:
  Invalid
Status in dpdk source package in Focal:
  Confirmed
Status in openvswitch source package in Focal:
  In Progress
Status in dpdk source package in Groovy:
  Confirmed
Status in openvswitch source package in Groovy:
  In Progress

Bug description:
  --- SRU-OVS ---

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

  [Test Case]
  The following SRU process was followed:
  https://wiki.ubuntu.com/OpenStackUpdates

  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.

  --- SRU DPDK for this bug ---

  [Impact]

  Due to changes landed in error in the 19.11 stable DPDK branch linking
  of OVS with DPDK is currently broken in Focal and Groovy.

  See http://mails.dpdk.org/archives/stable/2021-March/029418.html

  [Test Case]

  No change rebuild of the openvswitch package

  [Regression Potential]

  The offending commits should not have landed into the stable DPDK
  branch upstream; this has been discussed with developers involved with
  this change and it was agreed that they will be reverted.

  In theory one could say that the linking "now changes from 19.11.6" and
  that is correct. But that is an update-regression, not long in the archive
  and broke the primary in-archive-user being OVS. Therefore the benefit of reverting this outweighs this particular regression.

  --- SRU DPDK for the general MRE ---

  This bug tracks an update for the DPDK packages in:
  - Focal 19.11.6 -> 19.11.7
  - Groovy 19.11.6 -> 19.11.7

  Ready as of March 2021.

  17.11.x (Bionic) is no more getting such releases by upstream and
  20.11 (Hirsute) is new and up to date (20.11.1 will come to Hirsute in
  ~a month).

  This update includes bugfixes only following the SRU policy exception
  defined at https://wiki.ubuntu.com/StableReleaseUpdates/DPDK.

  No new features added, a classic stable release with a bunch of fixes
  aggregated and enhanced testing by the companies being part of the
  DPDK community.

  [Impact]

  Stable release update so not directly applicable; see the exception policy document linked above.
  For Reference - former cases are here:
  - https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1784816
  - https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1817675
  - https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1836365
  - https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1912464

  [Major Changes]

  As listed by upstream all is supposed to be fixes, no features:
  https://doc.dpdk.org/guides-19.11/rel_notes/release_19_11.html#id18

  [Test Plan]

  See https://wiki.ubuntu.com/StableReleaseUpdates/DPDK#SRU_TestVerify
  I'll attach a log of executing said tests from a ppa with the upload
  and explain why if there are any non passing tests.

  [Regression Potential]

  Upstream performs extensive testing before release, giving us a high
  degree of confidence in the general case. There problems are most
  likely to manifest in Ubuntu-specific integrations, such as in
  relation to the versions of dependencies available and other
  packaging-specific matters.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1920141/+subscriptions