MRE updates of dpdk 23.11.4(Noble)/21.11.9(Jammy)/23.11.4(oracular)/24.11.2(plucky)

[Miriam España Acebal]

23.11.1 for Oracular is in -proposed and nearly to be completed. Therefore the MREs for plucky, oracular, noble and jammy can be handled now (Oracular EOL will occur at the end of July, so we're trying to update it before it happens, but it might be optional at the end).

This bug tracks an update for the DPDK packages in:
- plucky 24.11.1 -> 24.11.2
- Oracular 23.11.2 -> 23.11.4
- Noble 23.11 -> 23.11.4
- Jammy 21.11.6 -> 21.11.9

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
- https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1940913
- https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/2002404
- https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/2026351

[Major Changes]

Listed by upstream in detail

Plucky - 24.11.2:
https://doc.dpdk.org/guides-24.11/rel_notes/release_24_11.html#id3

Oracular - 23.11.4:
https://doc.dpdk.org/guides-23.11/rel_notes/release_23_11.html#id9

Noble - 23.11.4:
https://doc.dpdk.org/guides-23.11/rel_notes/release_23_11.html#id9

Jammy - 21.11.9:
https://doc.dpdk.org/guides-21.11/rel_notes/release_21_11.html#id32

[Test Plan]

See https://wiki.ubuntu.com/StableReleaseUpdates/DPDK#SRU_TestVerify

[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.
Therefore that is what our verification focuses on.

[Christian Ehrhardt (paelzer)]

The issue in openvswitch tests with the new release has been fixed (Only Noble onwards).
See: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/2067889

You might coordinate with Frode if/when that will land in OVS in Noble.
That might be full 3.3.1 (if that is what they planned) or just the test fix and keeping it in block-proposed as it has no real value for the end user.

I heard nothing bad of 21.11.7 or 22.11.5 yet, so they should (tm) be fine.

Overall this should be unblocked for when you are back @mirespace

[Christian Ehrhardt (paelzer)]

Frode mentioned he will aim at doing the OVS upload in the next pulse. To track that I've opened bug 2069991 for him, which allows us to track it.

[Brian Murray (brian-murray)]

Ubuntu 23.10 (Mantic Minotaur) has reached end of life, so this bug will not be fixed for that specific release.

[Miriam España Acebal (mirespace)]

DPDK 23.11.2 is out (https://doc.dpdk.org/guides-23.11/rel_notes/release_23_11.html#id1), so this will be the version we prepare for Noble... Updating description.

[Miriam España Acebal (mirespace)]

Noble OK

Status log and log of testing dpdk standalone and in-conjunction with Open vSwitch (internal tests):

ubuntu@node-horsea:~/dpdk/testing/noble-oracular-cycle/dpdk-testing$ cat dpdk-test.status

PHYS_TESTPMD
VIRT_SPAWNGUESTS
VIRT_TESTPMD
VIRT_L2FWD
BENCH_OVS
VUC_BENCH_OVSDPDK
VUC_ENDURANCE_STARTSTOP
VUC_ENDURANCE_ADDREMOVEPORT

1.0.0 (13:51:11): phys (BM) tests
  1.1.0 (13:51:11): initialize environment
    1.1.1 (13:52:44): testpmd => Pass
    1.1.2 (13:53:37): check testpmd output => Pass
2.0.0 (13:53:37): prep virtual test environment

1.0.0 (13:56:11): virt tests
  1.1.0 (13:56:11): initialize environment
3.0.0 (13:57:02): performance tests
  3.1.0 (13:57:02): prep benchmarks
  3.2.0 (13:57:24): performance tests
    3.2.1 (13:57:33): test guest-openvswitch for OVS-5CPU => Pass
    3.2.2 (14:18:20): test guest-dpdk-vhost-user-client-multiq for OVSDPDK-VUC => Pass
4.0.0 (14:40:41): VUC endurance checks
  4.1.0 (14:40:41): prep VUC endurance tests
    4.1.1 (14:58:10): start stop guests (client) => Pass
    4.1.2 (16:03:20): add/remove ports (client) => Pass
  4.2.0 (16:12:48): Final cleanup

[Miriam España Acebal (mirespace)]

Jammy OK

Status log and log of testing dpdk standalone and in-conjunction with Open vSwitch (internal tests) for Jammy:

ubuntu@node-horsea:~/dpdk-testing$ cat dpdk-test.status

PHYS_TESTPMD
VIRT_SPAWNGUESTS
VIRT_TESTPMD
VIRT_L2FWD
BENCH_OVS
VUC_BENCH_OVSDPDK
VUC_ENDURANCE_STARTSTOP
VUC_ENDURANCE_ADDREMOVEPORT

1.0.0 (07:36:24): phys (BM) tests
  1.1.0 (07:36:24): initialize environment
    1.1.1 (07:37:23): testpmd => Pass
    1.1.2 (07:38:24): check testpmd output => Pass
2.0.0 (07:38:24): prep virtual test environment

1.0.0 (07:40:59): virt tests
  1.1.0 (07:40:59): initialize environment
3.0.0 (07:41:56): performance tests
  3.1.0 (07:41:56): prep benchmarks
  3.2.0 (07:42:45): performance tests
    3.2.1 (07:42:52): test guest-openvswitch for OVS-5CPU => Pass
    3.2.2 (08:02:19): test guest-dpdk-vhost-user-client-multiq for OVSDPDK-VUC => Pass
4.0.0 (08:21:52): VUC endurance checks
  4.1.0 (08:21:52): prep VUC endurance tests
    4.1.1 (08:35:38): start stop guests (client) => Pass
    4.1.2 (09:40:27): add/remove ports (client) => Pass

[Andreas Hasenack (ahasenack)]

Hello Miriam, or anyone else affected,

Accepted dpdk into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/dpdk/23.11.2-0ubuntu0.24.04.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-noble to verification-done-noble. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-noble. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

[Andreas Hasenack (ahasenack)]

Hello Miriam, or anyone else affected,

Accepted dpdk into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/dpdk/21.11.7-0ubuntu0.22.04.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-jammy. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

[Ubuntu SRU Bot (ubuntu-sru-bot)]

All autopkgtests for the newly accepted dpdk (21.11.7-0ubuntu0.22.04.1) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:

dpdk/unknown (ppc64el)

Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-migration/jammy/update_excuses.html#dpdk

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

[Christian Ehrhardt (paelzer)]

FYI the autopkgtests have been resolved quite a while ago.
What has held back the release was the physical shipment of our test machine to a different lab.

There now also likely is a competing upload (small change, not the same depth of verification needs) that might invalidate this and we might - for the MREs go for 23.11.3 and 21.11.9 once @mirespace prepared those in Q1 2024. Then hopefully with our testbed in place as needed for the larger changes that these updates represent.

[Marc Deslauriers (mdeslaur)]

Unfortunately, there was a security update published today to the existing packages, so we definitely need to respin the proposed packages to 23.11.3 and 21.11.9.

https://ubuntu.com/security/notices/USN-7178-1

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Christian Ehrhardt (paelzer)]

Thanks Marc,
we can respin with what we have now and do it all in one shot.

@Miriam - there were some duplicate bugs which made this appear even more work, I've close them all as dups to clear the view.

[Christian Ehrhardt (paelzer)]

Verification of this has been stuck for a while, we had shortages in regard to the associated people as well as a re-hosting of the test infrastructure.

Options here are either:
a) update this to the newer versions e.g. 23.11.4 is out already
b) run the recently fixed test automation against this (if only I'd not be a 2 week sprint next 2 weeks)

Ari contacted me and will have a look - thanks!

Once he concluded if we will go (a) or (b) I will try to use the testflinger based test against it (was not yet used to test against proposed).

[Arif Ali (arif-ali)]

I've created 4 MRs for SRU

1. jammy: 21.11.9 update
2. noble: 23.11.4 update
3. plucky: 24.11.2 update
4. oracular: 23.11.4 update

Not doing:

* mantic: EoL
* focal: already has the latest minor release

[Christian Ehrhardt (paelzer)]

Trying to work on this with Arif, updating tasks to remind me (imperfect)

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Christian Ehrhardt (paelzer)]

To re-confirm - yes these new uploads are meant to overwrite those that are already in [JN]-proposed. Our delay in verifying made them superseded by the next stable versions being released. And thanks to the help of Arif-Ali we can go for these right away.

In Debian we've released 24.11.2 and that already synced to questing, so we are SRU ready in that regard as well.

I've further recently fixed the automated testing and have some hope to be able to run them and Arif has a full scale setup he can run the code on as well for even better checking (at least on one release).

That being said I started into sponsor-reviewing the newly proposed versions.
After a while of reading and checking (see the linked MRs) it all looks good, uploading now ...

[Christian Ehrhardt (paelzer)]

All uploaded including pushing VCS info to ensure git-ubuntu can import the commits of Arif and to auto close the MRs once SRU-accepted.
Individual details (if ever needed) on the MRs.
These should all soon show up in [JNOP]-unapproved for the SRU team to look at.

[Christian Ehrhardt (paelzer)]

To confirm, I can see them like
https://launchpad.net/ubuntu/noble/+queue?queue_state=1&queue_text=dpdk

But the SRU team didn't yet get to it, being huge (actually not, but the pure diff lines are) probably has not helped to be picked up yet

[Nick Rosbrook (enr0n)]

Hello Miriam, or anyone else affected,

Accepted dpdk into plucky-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/dpdk/24.11.2-0ubuntu0.25.04.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-plucky to verification-done-plucky. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-plucky. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

[Nick Rosbrook (enr0n)]

Hello Miriam, or anyone else affected,

Accepted dpdk into oracular-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/dpdk/23.11.4-0ubuntu0.24.10.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-oracular to verification-done-oracular. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-oracular. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

[Nick Rosbrook (enr0n)]

Hello Miriam, or anyone else affected,

Accepted dpdk into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/dpdk/23.11.4-0ubuntu0.24.04.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-noble to verification-done-noble. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-noble. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

[Nick Rosbrook (enr0n)]

Hello Miriam, or anyone else affected,

Accepted dpdk into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/dpdk/21.11.9-0ubuntu0.22.04.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-jammy. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

[Ubuntu SRU Bot (ubuntu-sru-bot)]

All autopkgtests for the newly accepted dpdk (21.11.9-0ubuntu0.22.04.1) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:

dpdk/unknown (amd64)
openvswitch/unknown (amd64)

Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-migration/jammy/update_excuses.html#dpdk

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

[Ubuntu SRU Bot (ubuntu-sru-bot)]

All autopkgtests for the newly accepted dpdk (24.11.2-0ubuntu0.25.04.1) for plucky have finished running.
The following regressions have been reported in tests triggered by the package:

dpdk/unknown (amd64, i386, ppc64el)

Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-migration/plucky/update_excuses.html#dpdk

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

[Ubuntu SRU Bot (ubuntu-sru-bot)]

All autopkgtests for the newly accepted dpdk (23.11.4-0ubuntu0.24.10.1) for oracular have finished running.
The following regressions have been reported in tests triggered by the package:

dpdk/unknown (amd64, ppc64el)
openvswitch/3.4.0-1 (arm64)
openvswitch/unknown (amd64)
ovn/unknown (amd64, ppc64el)

Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-migration/oracular/update_excuses.html#dpdk

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

[Ubuntu SRU Bot (ubuntu-sru-bot)]

All autopkgtests for the newly accepted dpdk (23.11.4-0ubuntu0.24.04.1) for noble have finished running.
The following regressions have been reported in tests triggered by the package:

dpdk/unknown (amd64)
openvswitch/3.3.0-1ubuntu3.2 (ppc64el)
openvswitch/unknown (amd64)
ovn/unknown (amd64)

Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-migration/noble/update_excuses.html#dpdk

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

[Christian Ehrhardt (paelzer)]

I checked - all failing tests have been the infra giving up on us, restarted them and will recheck in a while.

[Christian Ehrhardt (paelzer)]

All but one autopkgtest issues resolved, the remaining one was a second tmpfail so far.

[Christian Ehrhardt (paelzer)]

FYI - Started the testflinger based regression test against noble (I can only pick one release per run so far)

[Christian Ehrhardt (paelzer)]

It was quicker than I expected, but
  $ testflinger-cli results e9a1c972-6443-425c-b134-7b4c80bbc863 | jq -r .test_output | less
shows no obvious breakage.

Going into the artifacts the different test stages save ...

  $ testflinger-cli artifacts e9a1c972-6443-425c-b134-7b4c80bbc863 --filename ~/Downloads/dpdk-test-noble-sru-13.06.2025.tgz

And then in the unpacked dir

  $ cat */execution-summary.log

PHYS_TESTPMD

1.0.0 (06:49:15): phys (BM) tests
  1.1.0 (06:49:15): initialize environment
    1.1.1 (06:52:21): testpmd => Pass
    1.1.2 (06:53:30): check testpmd output => Pass
  1.2.0 (06:53:30): Final cleanup
VIRT_SPAWNGUESTS
VIRT_TESTPMD

1.0.0 (06:53:41): phys (BM) tests
  1.1.0 (06:53:41): initialize environment
2.0.0 (06:54:44): prep virtual test environment

1.0.0 (06:56:53): virt tests
  1.1.0 (06:56:53): initialize environment
    1.1.1 (06:57:56): testpmd => Pass
    1.1.2 (06:58:50): check testpmd output => Pass
  2.1.0 (06:59:15): Final cleanup
VUC_BENCH_OVSDPDK

1.0.0 (06:59:27): phys (BM) tests
  1.1.0 (06:59:27): initialize environment
2.0.0 (07:00:39): prep virtual test environment
3.0.0 (07:01:21): performance tests
  3.1.0 (07:01:21): prep benchmarks
  3.2.0 (07:03:05): performance tests
    3.2.1 (07:03:16): test guest-dpdk-vhost-user-client-multiq for OVSDPDK-VUC => Pass
  3.3.0 (07:24:44): Final cleanup
VUC_ENDURANCE_STARTSTOP

1.0.0 (07:24:56): phys (BM) tests
  1.1.0 (07:24:56): initialize environment
2.0.0 (07:26:20): prep virtual test environment
3.0.0 (07:27:10): VUC endurance checks
  3.1.0 (07:27:10): prep VUC endurance tests
    3.1.1 (07:37:05): start stop guests (client) => Pass
  3.2.0 (08:41:34): Final cleanup
VUC_ENDURANCE_ADDREMOVEPORT

1.0.0 (08:41:45): phys (BM) tests
  1.1.0 (08:41:45): initialize environment
2.0.0 (08:43:09): prep virtual test environment
3.0.0 (08:43:59): VUC endurance checks
  3.1.0 (08:43:59): prep VUC endurance tests
    3.1.1 (08:46:08): add/remove ports (client) => Pass
  3.2.0 (08:55:31): Final cleanup

A lot of this testing has been adapted recently, let me make double sure we are using the right DPDK version from proposed as it is the first time executing against it ...

grep "DPDKVER" */execution-details.log
1-p-l2fwd/execution-details.log:+ DPDKVER=unknown
1-p-l2fwd/execution-details.log:+ DPDKVER=23.11.4-0ubuntu0.24.04.1
1-p-l2fwd/execution-details.log:++ DPDKVER=23.11.4-0ubuntu0.24.04.1
2-v-testpmd/execution-details.log:+ DPDKVER=unknown
2-v-testpmd/execution-details.log:+ DPDKVER=23.11.4-0ubuntu0.24.04.1
2-v-testpmd/execution-details.log:+ DPDKVER=unknown
2-v-testpmd/execution-details.log:+ DPDKVER=23.11-1ubuntu0.1
2-v-testpmd/execution-details.log:++ DPDKVER=23.11-1ubuntu0.1
3-v-ovsdpdk-speed/execution-details.log:+ DPDKVER=unknown
3-v-ovsdpdk-speed/execution-details.log:+ DPDKVER=23.11.4-0ubuntu0.24.04.1
3-v-ovsdpdk-speed/execution-details.log:++ DPDKVER=23.11.4-0ubuntu0.24.04.1
3-v-ovsdpdk-speed/execution-details.log:+ DPDKVER=23.11.4-0ubuntu0.24.04.1
3-v-ovsdpdk-speed/execution-details.log:+ DPDKVER=unknown
3-v-ovsdpdk-speed/execution-details.log:+ DPDKVER=unknown
4-v-ovsdpdk-startstop/execution-details.log:+ DPDKVER=unknown
4-v-ovsdpdk-startstop/execution-d...

[Christian Ehrhardt (paelzer)]

Actually I submitted jammy, oracular and plucky since TF can queue.
These target releases haven't been tested with the TF enabled test, need to check if they work right away or need fixes.

[Christian Ehrhardt (paelzer)]

As expected, Jammy tests completely failed due to the newer test not being ready for it (no actual DPDK fail), I'll need to work on that to get the run complete at some point.

For Plucky the machine didn't even deploy ?!, I've restarted that one as-is for now.

Oracular on the other hand was good.

cat artifacts/*/execution-summary.log

PHYS_TESTPMD

1.0.0 (10:19:18): phys (BM) tests
  1.1.0 (10:19:18): initialize environment
    1.1.1 (10:22:16): testpmd => Pass
    1.1.2 (10:23:27): check testpmd output => Pass
  1.2.0 (10:23:28): Final cleanup
VIRT_SPAWNGUESTS
VIRT_TESTPMD

1.0.0 (10:23:39): phys (BM) tests
  1.1.0 (10:23:39): initialize environment
2.0.0 (10:24:37): prep virtual test environment

1.0.0 (10:27:15): virt tests
  1.1.0 (10:27:15): initialize environment
    1.1.1 (10:28:14): testpmd => Pass
    1.1.2 (10:29:13): check testpmd output => Pass
  2.1.0 (10:29:39): Final cleanup
VUC_BENCH_OVSDPDK

1.0.0 (10:29:50): phys (BM) tests
  1.1.0 (10:29:50): initialize environment
2.0.0 (10:31:02): prep virtual test environment
3.0.0 (10:31:46): performance tests
  3.1.0 (10:31:46): prep benchmarks
  3.2.0 (10:33:10): performance tests
    3.2.1 (10:33:22): test guest-dpdk-vhost-user-client-multiq for OVSDPDK-VUC => Pass
  3.3.0 (10:54:07): Final cleanup
VUC_ENDURANCE_STARTSTOP

1.0.0 (10:54:19): phys (BM) tests
  1.1.0 (10:54:19): initialize environment
2.0.0 (10:55:47): prep virtual test environment
3.0.0 (10:56:37): VUC endurance checks
  3.1.0 (10:56:37): prep VUC endurance tests
    3.1.1 (11:11:08): start stop guests (client) => Pass
  3.2.0 (12:17:34): Final cleanup
VUC_ENDURANCE_ADDREMOVEPORT

1.0.0 (12:17:45): phys (BM) tests
  1.1.0 (12:17:45): initialize environment
2.0.0 (12:19:10): prep virtual test environment
3.0.0 (12:20:01): VUC endurance checks
  3.1.0 (12:20:01): prep VUC endurance tests
    3.1.1 (12:23:04): add/remove ports (client) => Pass
  3.2.0 (12:32:28): Final cleanup

And again confirming the version to be that of Oracular

paelzer 16:48:22 2 ~/Downloads grep "DPDKVER" artifacts/*/execution-details.log
artifacts/1-p-l2fwd/execution-details.log:+ DPDKVER=unknown
artifacts/1-p-l2fwd/execution-details.log:+ DPDKVER=23.11.4-0ubuntu0.24.10.1
artifacts/1-p-l2fwd/execution-details.log:++ DPDKVER=23.11.4-0ubuntu0.24.10.1
artifacts/2-v-testpmd/execution-details.log:+ DPDKVER=unknown
artifacts/2-v-testpmd/execution-details.log:+ DPDKVER=23.11.4-0ubuntu0.24.10.1
artifacts/2-v-testpmd/execution-details.log:+ DPDKVER=unknown
artifacts/2-v-testpmd/execution-details.log:+ DPDKVER=23.11.2-0ubuntu1.1
artifacts/2-v-testpmd/execution-details.log:++ DPDKVER=23.11.2-0ubuntu1.1
artifacts/3-v-ovsdpdk-speed/execution-details.log:+ DPDKVER=unknown
artifacts/3-v-ovsdpdk-speed/execution-details.log:+ DPDKVER=23.11.4-0ubuntu0.24.10.1
artifacts/3-v-ovsdpdk-speed/execution-details.log:++ DPDKVER=23.11.4-0ubuntu0.24.10.1
artifacts/3-v-ovsdpdk-speed/execution-details.log:+ DPDKVER=23.11.4-0ubuntu0.24.10.1
artifacts/3-v-ovsdpdk-speed/execution-details.log:+ DPDKVER=unknown
artifacts/3-v-ovsdpdk-speed/execution-details.log:+ DPDKVER=unknown
artifacts/4-v-ovsdpdk-startstop/execution-details.log:+ DPDKVER=unknown
artifacts/4-v-ovsdpdk...

[Christian Ehrhardt (paelzer)]

Jammy worked fine as well

artifacts/1-p-l2fwd/execution-summary.log

PHYS_TESTPMD

1.0.0 (15:31:45): phys (BM) tests
  1.1.0 (15:31:45): initialize environment
    1.1.1 (15:34:08): testpmd => Pass
    1.1.2 (15:35:16): check testpmd output => Pass
  1.2.0 (15:35:16): Final cleanup

artifacts/2-v-testpmd/execution-summary.log

VIRT_SPAWNGUESTS
VIRT_TESTPMD

1.0.0 (15:35:28): phys (BM) tests
  1.1.0 (15:35:28): initialize environment
2.0.0 (15:36:18): prep virtual test environment

1.0.0 (15:39:32): virt tests
  1.1.0 (15:39:32): initialize environment
    1.1.1 (15:41:02): testpmd => Pass
    1.1.2 (15:42:04): check testpmd output => Pass
  2.1.0 (15:42:26): Final cleanup

artifacts/3-v-ovsdpdk-speed/execution-summary.log

VUC_BENCH_OVSDPDK

1.0.0 (15:42:38): phys (BM) tests
  1.1.0 (15:42:38): initialize environment
2.0.0 (15:43:42): prep virtual test environment
3.0.0 (15:44:33): performance tests
  3.1.0 (15:44:33): prep benchmarks
  3.2.0 (15:45:23): performance tests
    3.2.1 (15:45:32): test guest-dpdk-vhost-user-client-multiq for OVSDPDK-VUC

artifacts/4-v-ovsdpdk-startstop/execution-summary.log

VUC_ENDURANCE_STARTSTOP

1.0.0 (15:54:46): phys (BM) tests
  1.1.0 (15:54:46): initialize environment
2.0.0 (15:56:03): prep virtual test environment
3.0.0 (15:57:00): VUC endurance checks
  3.1.0 (15:57:00): prep VUC endurance tests
    3.1.1 (16:17:33): start stop guests (client) => Pass
  3.2.0 (17:43:12): Final cleanup

artifacts/5-v-ovsdpdk-addremove/execution-summary.log

VUC_ENDURANCE_ADDREMOVEPORT

1.0.0 (17:43:24): phys (BM) tests
  1.1.0 (17:43:24): initialize environment
2.0.0 (17:44:37): prep virtual test environment
3.0.0 (17:45:34): VUC endurance checks
  3.1.0 (17:45:34): prep VUC endurance tests
    3.1.1 (17:49:53): add/remove ports (client) => Pass
  3.2.0 (17:59:24): Final cleanup

You can see that all passed except the expected "guest-dpdk-vhost-user-client-multiq for OVSDPDK-VUC" because that back then would still have to be set up with not vhost-user-client but vhost-user. That is no more meant to be exercised and hence drops out.

I checked the setup code manually and found the routes and simple traffic to work, but can not run the full benchmark on that sub-test.

All that was meant to pass passed, the rest worked on a (simpler) manual fallback check => Setting verification for Jammy.

For Plucky I still struggle to get the machine deployed.

[Christian Ehrhardt (paelzer)]

Turns out that the plucky run (Thanks Bjorn for fixing the MAAS deplyoment) runs into libvirt issues with the way we configure the system. The only way to debug that is to reserve it and run the same manual until we hit the

libvirt issue loading the apparmor profile when starting the guests that use the DPDK VUC code.
The only good thing for now is that this is very very unlikely due to the DPDK update, but it delays the verification on plucky.

[Christian Ehrhardt (paelzer)]

All autopkgtest issues resolved by now, the plucky verification is blocked for a few days more as virt tests consume the same machine.

[Christian Ehrhardt (paelzer)]

Plucky tests worked better now, two passed but still three issues in the test environment.

[Christian Ehrhardt (paelzer)]

Found more - still not DPDKs fault - test issues (workarounds for ongoing bugs that are not yet resolved in plucky, but known and in SRU processing). Applied a workaround for it to the tests and restarted the automated test.

[Christian Ehrhardt (paelzer)]

Finally tests are fine - again all was bit rot in the automation, no issue with the new upload.

Passed for all sub-tests

$ for f in artifacts/*/execution-summary.log ; do printf "\n\n\n\n$f\n"; cat $f; done

artifacts/1-p-l2fwd/execution-summary.log

PHYS_TESTPMD

1.0.0 (06:36:16): phys (BM) tests
  1.1.0 (06:36:16): initialize environment
    1.1.1 (06:39:20): testpmd => Pass
    1.1.2 (06:40:25): check testpmd output => Pass
  1.2.0 (06:40:25): Final cleanup

artifacts/2-v-testpmd/execution-summary.log

VIRT_SPAWNGUESTS
VIRT_TESTPMD

1.0.0 (06:40:36): phys (BM) tests
  1.1.0 (06:40:36): initialize environment
2.0.0 (06:41:34): prep virtual test environment

1.0.0 (06:43:43): virt tests
  1.1.0 (06:43:43): initialize environment
    1.1.1 (06:44:45): testpmd => Pass
    1.1.2 (06:45:40): check testpmd output => Pass
  2.1.0 (06:46:05): Final cleanup

artifacts/3-v-ovsdpdk-speed/execution-summary.log

VUC_BENCH_OVSDPDK

1.0.0 (06:46:16): phys (BM) tests
  1.1.0 (06:46:16): initialize environment
2.0.0 (06:47:33): prep virtual test environment
3.0.0 (06:48:25): performance tests
  3.1.0 (06:48:25): prep benchmarks
  3.2.0 (06:49:28): performance tests
    3.2.1 (06:49:38): test guest-dpdk-vhost-user-client-multiq for OVSDPDK-VUC => Pass
  3.3.0 (07:09:06): Final cleanup

artifacts/4-v-ovsdpdk-startstop/execution-summary.log

VUC_ENDURANCE_STARTSTOP

1.0.0 (07:09:18): phys (BM) tests
  1.1.0 (07:09:18): initialize environment
2.0.0 (07:10:48): prep virtual test environment
3.0.0 (07:11:48): VUC endurance checks
  3.1.0 (07:11:48): prep VUC endurance tests
    3.1.1 (07:21:12): start stop guests (client) => Pass
  3.2.0 (08:22:35): Final cleanup

artifacts/5-v-ovsdpdk-addremove/execution-summary.log

VUC_ENDURANCE_ADDREMOVEPORT

1.0.0 (08:22:46): phys (BM) tests
  1.1.0 (08:22:46): initialize environment
2.0.0 (08:24:14): prep virtual test environment
3.0.0 (08:25:16): VUC endurance checks
  3.1.0 (08:25:16): prep VUC endurance tests
    3.1.1 (08:27:13): add/remove ports (client) => Pass
  3.2.0 (08:36:31): Final cleanup

And as before making sure we tested what is in proposed here

$ grep "DPDKVER" artifacts/*/execution-details.log
artifacts/1-p-l2fwd/execution-details.log:+ DPDKVER=unknown
artifacts/1-p-l2fwd/execution-details.log:+ DPDKVER=24.11.2-0ubuntu0.25.04.1
artifacts/1-p-l2fwd/execution-details.log:++ DPDKVER=24.11.2-0ubuntu0.25.04.1
artifacts/2-v-testpmd/execution-details.log:+ DPDKVER=unknown
artifacts/2-v-testpmd/execution-details.log:+ DPDKVER=24.11.2-0ubuntu0.25.04.1
artifacts/2-v-testpmd/execution-details.log:+ DPDKVER=unknown
artifacts/2-v-testpmd/execution-details.log:+ DPDKVER=24.11.1-1
artifacts/2-v-testpmd/execution-details.log:++ DPDKVER=24.11.1-1
artifacts/3-v-ovsdpdk-speed/execution-details.log:+ DPDKVER=unknown
artifacts/3-v-ovsdpdk-speed/execution-details.log:+ DPDKVER=24.11.2-0ubuntu0.25.04.1
artifacts/3-v-ovsdpdk-speed/execution-details.log:++ DPDKVER=24.11.2-0ubuntu0.25.04.1
artifacts/3-v-ovsdpdk-speed/execution-details.log:+ DPDKVER=24.11.2-0ubuntu0.25.04.1
artifacts/3-v-ovsdpdk-speed/execution-details.log:+ DPDKVER=unknown
artifacts/3-v-ovsdpdk-speed/execution-details.log:+ DPDKVER=unknown
arti...

[Christian Ehrhardt (paelzer)]

- OK, thereby all releases have been verified with the test suite as planned.
- Autopkgtests are also all happy by now.
- pending SRU lists them as happy and aging for 11 days

So this should be ready to be released as time permits.

[Launchpad Janitor (janitor)]

This bug was fixed in the package dpdk - 24.11.2-0ubuntu0.25.04.1

---------------
dpdk (24.11.2-0ubuntu0.25.04.1) plucky; urgency=medium

  * Merge stable release 24.11.2 (LP: #2067480)
    - Full release notes are available at:
      https://doc.dpdk.org/guides-24.11/rel_notes/release_24_11.html#id1

 -- Arif Ali <email address hidden> Tue, 06 May 2025 06:56:35 +0000

[Timo Aaltonen (tjaalton)]

The verification of the Stable Release Update for dpdk has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

[Launchpad Janitor (janitor)]

This bug was fixed in the package dpdk - 23.11.4-0ubuntu0.24.10.1

---------------
dpdk (23.11.4-0ubuntu0.24.10.1) oracular; urgency=medium

  * Merge stable release 23.11.4 (LP: #2067480)
    - Full release notes are available at:
      https://doc.dpdk.org/guides-23.11/rel_notes/release_23_11.html#id9

  * d/p/CVE-2024-11614.patch:
    Removal of patch, as this is now resolved in source.

 -- Arif Ali <email address hidden> Tue, 06 May 2025 06:56:35 +0000

[Launchpad Janitor (janitor)]

This bug was fixed in the package dpdk - 23.11.4-0ubuntu0.24.04.1

---------------
dpdk (23.11.4-0ubuntu0.24.04.1) noble; urgency=medium

  * Merge LTS stable release 23.11.4 (LP: #2067480)
    - Full release notes are available at:
      https://doc.dpdk.org/guides-23.11/rel_notes/release_23_11.html#id9

 -- Arif Ali <email address hidden> Tue, 06 May 2025 06:56:35 +0000

[Launchpad Janitor (janitor)]

This bug was fixed in the package dpdk - 21.11.9-0ubuntu0.22.04.1

---------------
dpdk (21.11.9-0ubuntu0.22.04.1) jammy; urgency=medium

  * Merge LTS stable release 21.11.9 (LP: #2067480)
    - Full release notes are available at:
      https://doc.dpdk.org/guides-21.11/rel_notes/release_21_11.html#id32

 -- Arif Ali <email address hidden> Tue, 06 May 2025 06:56:35 +0000