[Bug 2120204] Re: [SRU] MariaDB 11.4.8, 10.11.14, 10.6.23 in all maintained Ubuntu releases

Fri Dec 5 23:51:20 UTC 2025

Reviewing autopkgtest logs:

libdbd-mariadb-perl/1.22-1ubuntu1 (arm64)

153s autopkgtest [16:39:43]: test pkg-perl-autopkgtest-build-deps-mariadb: -----------------------]
155s autopkgtest [16:39:45]: test pkg-perl-autopkgtest-build-deps-mariadb:  - - - - - - - - - - results - - - - - - - - - -
155s pkg-perl-autopkgtest-build-deps-mariadb PASS
...
243s Investigating (0) mysql-server:arm64 < none -> 8.4.7-0ubuntu0.25.04.2 @un puN Ib >
243s Broken mysql-server:arm64 Conflicts on mariadb-common:arm64 < none -> 1:11.4.8-0ubuntu0.25.04.1 @un puN >
243s   Considering mariadb-common:arm64 -1 as a solution to mysql-server:arm64 0
243s   Conflicts//Breaks against version 1:11.4.7-0ubuntu0.25.04.1 for mariadb-common but that is not InstVer, ignoring
243s   Conflicts//Breaks against version 1:11.4.5-1 for mariadb-common but that is not InstVer, ignoring
243s Done
243s Some packages could not be installed. This may mean that you have
243s requested an impossible situation or if you are using the unstable
243s distribution that some required packages have not yet been created
243s or been moved out of Incoming.
243s The following information may help to resolve the situation:
243s 
243s The following packages have unmet dependencies:
244s  mysql-server : Conflicts: mariadb-common but 1:11.4.8-0ubuntu0.25.04.1 is to be installed
244s E: Unable to correct problems, you have held broken packages.
...
595s ERROR (CommandError): No server with a name or ID of '866047de-09d2-41df-bd79-1678a5f184d7' exists.
595s ---------------------------------------------------
595s ------- nova show 866047de-09d2-41df-bd79-1678a5f184d7 (adt-plucky-arm64-libdbd-mariadb-perl-20251205-150806-juju-7f2275-prod-proposed-migration-environment-2-30027a06-26ce-4d00-b0bf-2678e12f2c82) ------
597s ERROR (CommandError): No server with a name or ID of '866047de-09d2-41df-bd79-1678a5f184d7' exists.
597s ---------------------------------------------------
993s sudo-rs: '/tmp/autopkgtest-run-wrapper': command not found
997s <VirtSubproc>: failure: failed to run setup script '/home/ubuntu/autopkgtest/ssh-setup/nova' with command 'revert'
998s autopkgtest [16:53:48]: ERROR: testbed failure: eof from the virtualisation server

While there seems to be something going on with the testbed, there is
also a genuine looking conflict "mysql-server : Conflicts: mariadb-
common". Oddly this is only visible on the arm64 autopkgtest, not on any
other platform. Also this MariaDB update didn't include any
debian/control file changes, so it can't be the source of such a package
conflict.

mariadb-connector-odbc/3.1.15-3 (s390x)

 55s Setting up mariadb-client-core (1:11.4.8-0ubuntu0.25.04.1) ...
 55s Setting up odbc-mariadb (3.1.15-3) ...
 55s odbcinst: Driver installed. Usage count increased to 1. 
 55s     Target directory is /etc
 55s Setting up mariadb-server-core (1:11.4.8-0ubuntu0.25.04.1) ...
 55s Setting up mariadb-client (1:11.4.8-0ubuntu0.25.04.1) ...
 55s Setting up mariadb-server (1:11.4.8-0ubuntu0.25.04.1) ...
 56s Created symlink '/etc/systemd/system/multi-user.target.wants/mariadb.service' → '/usr/lib/systemd/system/mariadb.service'.

 58s Processing triggers for man-db (2.13.0-1) ...
 58s Processing triggers for libc-bin (2.41-6ubuntu1.2) ...
 59s autopkgtest [16:12:10]: test mysql-query: [-----------------------
 60s Creating test database
 60s ERROR 2026 (HY000): TLS/SSL error: certificate is not yet valid
 60s autopkgtest [16:12:11]: test mysql-query: -----------------------]
 60s autopkgtest [16:12:11]: test mysql-query:  - - - - - - - - - - results - - - - - - - - - -
 60s mysql-query          FAIL non-zero exit status 1
 60s autopkgtest [16:12:11]: test mysql-query:  - - - - - - - - - - stderr - - - - - - - - - -
 61s ERROR 2026 (HY000): TLS/SSL error: certificate is not yet valid
 61s autopkgtest [16:12:12]: @@@@@@@@@@@@@@@@@@@@ summary
 61s mysql-query          FAIL non-zero exit status 1

Weird TLS cert issue, and only on a single architecture. Could the host
clock be squewed or something?

mediawiki-extension-youtube/1.9.3~git20221020.e005c0b-1ubuntu1 (amd64)

118s autopkgtest [16:56:37]: test lint: -----------------------]
119s lint                 PASS
119s autopkgtest [16:56:38]: test lint:  - - - - - - - - - - results - - - - - - - - - -
119s autopkgtest [16:56:38]: test install-sqlite: preparing testbed
141s Creating nova instance adt-plucky-amd64-mediawiki-extension-youtube-20251205-145917-juju-7f2275-prod-proposed-migration-environment-2-850180e6-cff6-4e76-9d60-75878691de24 from image adt/ubuntu-plucky-amd64-server-20251205.img (UUID 00beb220-ebfa-480a-a1b5-b746096362b4)...
463s nova [E] nova boot failed (attempt #0):
...
466s ERROR (CommandError): No server with a name or ID of '5b383756-063c-4767-b5d4-46886f802fbb' exists.
466s ---------------------------------------------------
466s ------- nova show 5b383756-063c-4767-b5d4-46886f802fbb (adt-plucky-amd64-mediawiki-extension-youtube-20251205-145917-juju-7f2275-prod-proposed-migration-environment-2-850180e6-cff6-4e76-9d60-75878691de24) ------
468s ERROR (CommandError): No server with a name or ID of '5b383756-063c-4767-b5d4-46886f802fbb' exists.
469s ---------------------------------------------------
3096s <VirtSubproc>: failure: failed to run setup script '/home/ubuntu/autopkgtest/ssh-setup/nova' with command 'revert'
3096s autopkgtest [17:46:15]: ERROR: testbed failure: eof from the virtualisation server

Testbed issue?

mediawiki-skin-greystuff/1.2.5~git20220922.60bda8c-2ubuntu1 (amd64)

126s autopkgtest [16:48:40]: test lint: -----------------------]
127s lint                 PASS
127s autopkgtest [16:48:41]: test lint:  - - - - - - - - - - results - - - - - - - - - -
127s autopkgtest [16:48:41]: test install-sqlite: preparing testbed
150s Creating nova instance adt-plucky-amd64-mediawiki-skin-greystuff-20251205-145920-juju-7f2275-prod-proposed-migration-environment-2-7f0ec615-89f9-4946-b60c-83ac1085510a from image adt/ubuntu-plucky-amd64-server-20251205.img (UUID 00beb220-ebfa-480a-a1b5-b746096362b4)...
471s nova [E] nova boot failed (attempt #0):
...
473s ERROR (CommandError): No server with a name or ID of 'ca697dd8-c444-4fe4-8618-cde837610808' exists.
473s ---------------------------------------------------
473s ------- nova show ca697dd8-c444-4fe4-8618-cde837610808 (adt-plucky-amd64-mediawiki-skin-greystuff-20251205-145920-juju-7f2275-prod-proposed-migration-environment-2-7f0ec615-89f9-4946-b60c-83ac1085510a) ------
476s ERROR (CommandError): No server with a name or ID of 'ca697dd8-c444-4fe4-8618-cde837610808' exists.
476s ---------------------------------------------------
3103s <VirtSubproc>: failure: failed to run setup script '/home/ubuntu/autopkgtest/ssh-setup/nova' with command 'revert'
3103s autopkgtest [17:38:17]: ERROR: testbed failure: eof from the virtualisation server

Same issue as above. Seems test or testbed related, no signs of a
regression in MariaDB.

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