[Bug 1829347] Re: systemd autopkgtest 'storage' fails adding/rmmoding scsi_debug
Dan Streetman
dan.streetman at canonical.com
Thu May 16 10:27:02 UTC 2019
** Changed in: systemd (Ubuntu Eoan)
Assignee: (unassigned) => Dan Streetman (ddstreet)
** Changed in: systemd (Ubuntu Disco)
Assignee: (unassigned) => Dan Streetman (ddstreet)
** Changed in: systemd (Ubuntu Cosmic)
Assignee: (unassigned) => Dan Streetman (ddstreet)
** Changed in: systemd (Ubuntu Bionic)
Assignee: (unassigned) => Dan Streetman (ddstreet)
** Changed in: systemd (Ubuntu Eoan)
Status: New => In Progress
** Changed in: systemd (Ubuntu Disco)
Status: New => In Progress
** Changed in: systemd (Ubuntu Cosmic)
Status: New => In Progress
** Changed in: systemd (Ubuntu Bionic)
Status: New => In Progress
** Changed in: systemd (Ubuntu Eoan)
Importance: Undecided => Medium
** Changed in: systemd (Ubuntu Disco)
Importance: Undecided => Medium
** Changed in: systemd (Ubuntu Cosmic)
Importance: Undecided => Medium
** Changed in: systemd (Ubuntu Bionic)
Importance: Undecided => Medium
** Description changed:
[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)
+ 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.
+ or for older releases something like:
+
+ autopkgtest [19:27:26]: test storage: [-----------------------
+ modprobe: FATAL: Module scsi_debug not found in directory /lib/modules/4.18.0-1011-kvm
+ ERROR
+
+ ======================================================================
+ ERROR: setUpClass (__main__.CryptsetupTest)
+ ----------------------------------------------------------------------
+ Traceback (most recent call last):
+ File "/tmp/autopkgtest.azsL0q/build.Hbd/src/debian/tests/storage", line 21, in setUpClass
+ subprocess.check_call(['modprobe', 'scsi_debug'])
+ File "/usr/lib/python3.6/subprocess.py", line 291, in check_call
+ raise CalledProcessError(retcode, cmd)
+ subprocess.CalledProcessError: Command '['modprobe', 'scsi_debug']' returned non-zero exit status 1.
+
+
+ this has attempted to be fixed in disco/eoan 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.
** Tags added: ddstreet-next
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, 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:
In Progress
Status in systemd source package in Bionic:
In Progress
Status in systemd source package in Cosmic:
In Progress
Status in systemd source package in Disco:
In Progress
Status in systemd source package in Eoan:
In Progress
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
or for older releases something like:
autopkgtest [19:27:26]: test storage: [-----------------------
modprobe: FATAL: Module scsi_debug not found in directory /lib/modules/4.18.0-1011-kvm
ERROR
======================================================================
ERROR: setUpClass (__main__.CryptsetupTest)
----------------------------------------------------------------------
Traceback (most recent call last):
File "/tmp/autopkgtest.azsL0q/build.Hbd/src/debian/tests/storage", line 21, in setUpClass
subprocess.check_call(['modprobe', 'scsi_debug'])
File "/usr/lib/python3.6/subprocess.py", line 291, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['modprobe', 'scsi_debug']' returned non-zero exit status 1.
this has attempted to be fixed in disco/eoan 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
More information about the foundations-bugs
mailing list