[Bug 2129196] Autopkgtest regression report (mysql-8.0/8.0.44-0ubuntu0.24.04.2)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted mysql-8.0 (8.0.44-0ubuntu0.24.04.2) for noble have finished running.
The following regressions have been reported in tests triggered by the package:

bacula/13.0.4-1build3 (armhf)
exim4/4.97-4ubuntu4.3 (ppc64el)
freeradius/3.2.5+dfsg-3~ubuntu24.04.3 (armhf)
glance/2:28.1.0-0ubuntu1 (armhf)
hoel/1.4.29-1.1build2 (armhf)
isc-kea/2.4.1-3ubuntu0.1 (s390x)
watcher/2:12.0.0-0ubuntu1 (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/noble/update_excuses.html#mysql-8.0

[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/2129196

Title:
  mysql-server fails to install when an ext4 fs is mounted to
  /var/lib/mysql

Status in mysql-8.0 package in Ubuntu:
  New
Status in mysql-8.4 package in Ubuntu:
  Fix Released
Status in mysql-8.0 source package in Jammy:
  Fix Committed
Status in mysql-8.0 source package in Noble:
  Fix Committed
Status in mysql-8.4 source package in Plucky:
  Fix Committed
Status in mysql-8.4 source package in Questing:
  Fix Committed
Status in mysql-8.4 source package in Resolute:
  Fix Released

Bug description:
  [ Impact ]

   * The postinst script for mysql-server checks whether the
  `/var/lib/mysql` directory is empty before setting up the database
  state. When `/var/lib/mysql` is an ext4 filesystem, the `lost+found`
  directory causes this check to fail and the database is not properly
  set up.

   * Mounting a separate volume to hold the mysql state is a common
  pattern, and ext4 is extremely prevalent so this is likely to be a
  common pain point. Although workarounds are straightforward, it makes
  for bad UX.

   * This can be remedied by ignoring the lost+found directory in the
  check.

  [ Test Plan ]

   To ensure bug is fixed:
   * Create an empty ext4 volume and mount it to /var/lib/mysql
   * Install mysql-server
   * Check whether the installation succeeds

   To check that data is preserved:
   * Uninstall and reinstall mysql-server
   * Ensure that the data in /var/lib/mysql is not overwritten

  [ Where problems could occur ]

   * In this case, the only change is to the postinst script, so problems should be related to install.
   * If the check being done were incorrect it could lead to loss of user data.
     - We keep the change to script to a minimum to reduce the risk of this
     - Test plan includes confirming that user data is not overwritten

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/2129196/+subscriptions