[Bug 1814373] Re: storage / luks / dmsetup regressed (or got better) on ppc64le

[Dan Streetman]

** Bug watch added: Debian Bug tracker #929726
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929726

** Also affects: systemd (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929726
   Importance: Unknown
       Status: Unknown

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

Title:
  storage / luks / dmsetup regressed (or got better) on ppc64le

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  In Progress
Status in udisks2 package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  New
Status in systemd source package in Bionic:
  In Progress
Status in udisks2 source package in Bionic:
  Invalid
Status in linux source package in Cosmic:
  New
Status in systemd source package in Cosmic:
  In Progress
Status in udisks2 source package in Cosmic:
  Invalid
Status in linux source package in Disco:
  New
Status in systemd source package in Disco:
  In Progress
Status in udisks2 source package in Disco:
  Invalid
Status in linux source package in Eoan:
  Confirmed
Status in systemd source package in Eoan:
  In Progress
Status in udisks2 source package in Eoan:
  Invalid
Status in systemd package in Debian:
  Unknown

Bug description:
  in disco proposed with new systemd and v4.19 kernel it appears that
  dmsetup / cryptsetup storage either got better or worse.

  Devices take very long to activate, and sometimes remain in use during
  test clean up.

  This leads to udisks autopkgtest failing on ppc64le and systemd's
  "storage" autopkgtest is also failing.

  I've tried to make ppc64le test more resilient, but it's still odd
  that it became unstable in disco, and used to be rock solid on
  ppc64le.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814373/+subscriptions