Public bug reported:
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.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Affects: udisks (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Also affects: udisks (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1814373
Title:
storage / luks / dmsetup regressed (or got better) on ppc64le
Status in linux package in Ubuntu:
New
Status in systemd package in Ubuntu:
New
Status in udisks package in Ubuntu:
New
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
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
