This bug was fixed in the package multipath-tools - 0.6.4-3ubuntu1
---
multipath-tools (0.6.4-3ubuntu1) zesty; urgency=medium
* Merge from Debian. (LP: #1621340, LP: #1645274) Remaining changes:
- d/control:
- Bump udev dependencies
- multipath-udeb: add sg3-udeb
** Merge proposal linked:
https://code.launchpad.net/~paelzer/ubuntu/+source/multipath-tools/+git/multipath-tools/+merge/311921
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1644253
Title:
** Changed in: multipath-tools (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1644253
Title:
multipath-tool autopkg test fail on s390
To manage
** Changed in: multipath-tools (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1644253
Title:
multipath-tool autopkg test fail on s390
To manage
Ok, discussion showed that there is still a LXD in between - thanks
xnox.
That said the flags of the tests are incomplete, it needs isolation-
machine.
Not considering SRU, once *stack infratstruture is used they will start
to work for X
--
You received this bug notification because you are a
s390x autopkgtest is the only autopkgtests that run in LXD containers
unpriviledged, unlike all other autopkgtests. Thus please use isolation-
machine for now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Worked on s390x LPAR as well as in an s390x KVM guest just as is.
I think it is related to
/dev/mapper/control: open failed: Operation not permitted
Failure to communicate with kernel device-mapper driver.
Check that device-mapper is available in the kernel.
Incompatible libdevmapper 1.02.136
