Public bug reported: [impact]
systemd autopkgtest fails [test case] run systemd autopkgtest, check for output like: LUKS device with "tmp" option ... rmmod: ERROR: Module scsi_debug is in use FAIL ====================================================================== FAIL: test_luks_tmp (__main__.CryptsetupTest) LUKS device with "tmp" option ---------------------------------------------------------------------- Traceback (most recent call last): File "/tmp/autopkgtest.It858Q/build.e7O/src/debian/tests/storage", line 59, in setUp self.fail('%s exists already' % self.plaintext_dev) AssertionError: /dev/mapper/testcrypt1 exists already this has attempted to be fixed in various ways so the output is a bit different across different releases, but all of them have the common point of failing to modprobe or rmmod the scsi_debug module, which by itself doesn't indicate a failure. [regression potential] low; this is fixing a testcase only. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1829347 Title: systemd autopkgtest 'storage' fails adding/rmmoding scsi_debug Status in systemd package in Ubuntu: New Bug description: [impact] systemd autopkgtest fails [test case] run systemd autopkgtest, check for output like: LUKS device with "tmp" option ... rmmod: ERROR: Module scsi_debug is in use FAIL ====================================================================== FAIL: test_luks_tmp (__main__.CryptsetupTest) LUKS device with "tmp" option ---------------------------------------------------------------------- Traceback (most recent call last): File "/tmp/autopkgtest.It858Q/build.e7O/src/debian/tests/storage", line 59, in setUp self.fail('%s exists already' % self.plaintext_dev) AssertionError: /dev/mapper/testcrypt1 exists already this has attempted to be fixed in various ways so the output is a bit different across different releases, but all of them have the common point of failing to modprobe or rmmod the scsi_debug module, which by itself doesn't indicate a failure. [regression potential] low; this is fixing a testcase only. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1829347/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp