i thought for sure it would be a systemd bug and/or testcase bug :)

** Changed in: systemd (Ubuntu Eoan)
       Status: In Progress => New

** Changed in: systemd (Ubuntu Eoan)
     Assignee: Dan Streetman (ddstreet) => (unassigned)

** Changed in: systemd (Ubuntu Disco)
       Status: In Progress => New

** Changed in: systemd (Ubuntu Disco)
     Assignee: Dan Streetman (ddstreet) => (unassigned)

** Changed in: systemd (Ubuntu Bionic)
       Status: In Progress => New

** Changed in: systemd (Ubuntu Bionic)
     Assignee: Dan Streetman (ddstreet) => (unassigned)

** Changed in: systemd (Ubuntu Xenial)
       Status: In Progress => New

** Changed in: systemd (Ubuntu Xenial)
     Assignee: Dan Streetman (ddstreet) => (unassigned)

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

Title:
  systemd 229-4ubuntu21.22 ADT test failure with linux 4.4.0-156.183
  (storage)

Status in linux package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  New
Status in linux source package in Xenial:
  In Progress
Status in systemd source package in Xenial:
  New
Status in linux source package in Bionic:
  Invalid
Status in systemd source package in Bionic:
  New
Status in linux source package in Disco:
  Invalid
Status in systemd source package in Disco:
  New
Status in linux source package in Eoan:
  Invalid
Status in systemd source package in Eoan:
  New

Bug description:
  Testing failed on:
      i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/s/systemd/20190719_145555_3528c@/log.gz

  The storage testcase is failing on i386. Running the testcase
  manually, it hangs at:

  systemd-229/debian/tests$ sudo ./storage 
  test_luks_by_devname (__main__.CryptsetupTest)
  LUKS device by plain device name, empty ... Please enter passphrase for disk 
testcrypt1! 

  Looking at the storage testcase, on function start_password_agent(),
  it expects the 'disk scsi_debug' string on the systemd ask-password
  file, however the contains:

  Message=Please enter passphrase for disk testcrypt1!

  That doesn't seems to happen on other architectures. On amd64, the
  testcase output is:

  systemd-229/debian/tests$ sudo ./storage 
  test_luks_by_devname (__main__.CryptsetupTest)
  LUKS device by plain device name, empty ... Please enter passphrase for disk 
scsi_debug (testcrypt1)! 
  ok
  [...]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1837235/+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

Reply via email to