** Patch added: "lp1757107.diff" https://bugs.launchpad.net/ubuntu/+source/mariadb-10.1/+bug/1757107/+attachment/5085457/+files/lp1757107.diff
** Description changed: + [Impact] + + - In debian/rules, -pie introduced, yet previously the build was fully + hardened. (I believe this is cosmetic, as supposedly the build system + defaults to pie anyway) + + - There used to be a default client socket set, but not anymore. + + - Most importantly, the dh_systemd_start workarounds were dropped; yet + are still needed on artful, as otherwise after server installation the + unit is not started / not running + + - Due to last one, autopkgtests are failing - see + http://autopkgtest.ubuntu.com/packages/mariadb-10.1 and thus blocking + releasing other SRUs, e.g. systemd one. + + [Solution] + + - perform partial revert of packaging changes, back to what it was + before (all the hacks & workarounds included) + + [Testcase] + + - autopkgtests should pass for mariadb-10.1 package, specifically the + smoke test case + + [Regression Potential] + Reverting packaging changes introduced in the last update; back to what they were before and what they are in the release pocket. This revert may have been done incorrectly, thus yielding more maintainer script bugs, but interactive testing of this revert appears to be functioning correctly. + + [Original Bug report] + + + 10.1.30-0ubuntu0.17.10.1 upload of mariadb-10.1 regresses autopkgtest smoke test like so: Setting up mariadb-server-core-10.1 (10.1.30-0ubuntu0.17.10.1) ... Setting up mariadb-client-core-10.1 (10.1.30-0ubuntu0.17.10.1) ... Setting up mariadb-client-10.1 (10.1.30-0ubuntu0.17.10.1) ... Setting up mariadb-server-10.1 (10.1.30-0ubuntu0.17.10.1) ... Created symlink /etc/systemd/system/mysql.service → /lib/systemd/system/mariadb.service. Created symlink /etc/systemd/system/mysqld.service → /lib/systemd/system/mariadb.service. Created symlink /etc/systemd/system/multi-user.target.wants/mariadb.service → /lib/systemd/system/mariadb.service. Setting up autopkgtest-satdep (0) ... Processing triggers for libc-bin (2.26-0ubuntu2.1) ... Processing triggers for systemd (234-2ubuntu12.3) ... (Reading database ... 69452 files and directories currently installed.) Removing autopkgtest-satdep (0) ... autopkgtest [00:52:38]: test smoke: [----------------------- + mysql ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2 "No such file or directory") autopkgtest [00:52:39]: test smoke: -----------------------] autopkgtest [00:52:39]: test smoke: - - - - - - - - - - results - - - - - - - - - - smoke FAIL non-zero exit status 1 - Looks like the server is not started ? It appears so, at least reproducible in lxd container. There are maintainer scripts to start init.d script, however that is not done for systemd. I do not se for example deb-systemd-helper start mariadb.service at all. Possibly regression due to using a new/different debhelper during package build. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1757107 Title: Security update 10.1.30-0ubuntu0.17.10.1 regresses smoke test, mariadb not started upon install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mariadb-10.1/+bug/1757107/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
