[Bug 2120204] Autopkgtest regression report (mariadb-10.6/1:10.6.23-0ubuntu0.22.04.1)

[Ubuntu SRU Bot]

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

dbconfig-common/2.0.21 (armhf)
mariadb-10.6/1:10.6.23-0ubuntu0.22.04.1 (armhf)


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#mariadb-10.6

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

Thank you!

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/2120204

Title:
  [SRU] MariaDB 11.4.8, 10.11.14, 10.6.23 in all maintained Ubuntu
  releases

Status in mariadb package in Ubuntu:
  Confirmed
Status in mariadb-10.6 package in Ubuntu:
  Invalid
Status in mariadb source package in Jammy:
  Invalid
Status in mariadb-10.6 source package in Jammy:
  Fix Committed
Status in mariadb source package in Noble:
  Fix Committed
Status in mariadb source package in Plucky:
  Fix Committed

Bug description:
  This issue tracks an update for the MariaDB and Galera packages,
  moving to versions:

  * questing (25.10): MariaDB 1:11.8.3
  * plucky (25.04): MariaDB 1:11.4.8
  * noble (24.04): MariaDB 1:10.11.14
  * jammy (22.04): MariaDB 1:10.6.23

  These minor maintenance releases include bug fixes following the SRU special case documentation at
  https://documentation.ubuntu.com/sru/en/latest/reference/exception-MariaDB-Galera-Updates/.

  Upstream did not announce any new CVEs fixed by this release, so these
  versions will not be uploaded as security updates, but as regular
  stable updates.

  [Upstream changes]

  The new versions, along with descriptions of changes and detailed
  changelogs for each version will be posted as MRs
  https://salsa.debian.org/mariadb-team/mariadb-server/

  So far the 11.8.3 import to Debian unstable (and Ubuntu devel) has
  been posted for review at https://salsa.debian.org/mariadb-
  team/mariadb-server/-/merge_requests/129

  [Test Plan]

  TODO: Check that builds pass on all Ubuntu architectures
  TODO: Check that the full build passed, including checks for file locations,
        symbols file and ABI stability and the post-build upstream tests
  TODO: Check DEP-8 (autopkgtests) pass
  TODO: If that the same update in Debian unstable and Ubuntu devel passed all
        QA systems, including DEP-8 (autopkgtests) for reverse dependencies
  TODO: If there are any non passing tests - explain why that is ok in this case
  TODO: Add results of an autopkgtest run against all the new versions
  TODO: If available, check status of Debian Salsa pipelines

  [Regression Potential]

  The build incorporates an extensive build and integration test suite. The
  upstream also releases their own .deb packages and they too run extensive
  tests on them. Regressions would likely arise from a change in interaction
  with Ubuntu-specific integrations.

  Some regressions were already discovered while preparing
  https://salsa.debian.org/mariadb-team/mariadb-
  server/-/merge_requests/129 and patched to partially revert some
  upstream changes.

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