multipath-tool autopkg test fail on s390
Bug #1644253 reported by
Christian Ehrhardt
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
multipath-tools (Ubuntu) |
Fix Released
|
Medium
|
Unassigned |
Bug Description
Hi,
I just happened to see that multipath-tools autpkgtest is on "always failed" on s390x.
For a platform that so heavily relies on multipath-tools that should be fixed on next merge.
Here is one example:
https:/
You can pick whatever is the latest from:
http://
P.S. the same is true for armhf but they are less "multipathy" IMHO.
Changed in multipath-tools (Ubuntu): | |
status: | New → Confirmed |
importance: | Undecided → Medium |
Changed in multipath-tools (Ubuntu): | |
status: | Confirmed → Triaged |
Changed in multipath-tools (Ubuntu): | |
status: | Triaged → In Progress |
To post a comment you must log in.
Worked on s390x LPAR as well as in an s390x KVM guest just as is.
I think it is related to control: open failed: Operation not permitted
/dev/mapper/
Failure to communicate with kernel device-mapper driver.
Check that device-mapper is available in the kernel.
Incompatible libdevmapper 1.02.136 (2016-11-05) and kernel driver (unknown version).
The script runs with needs-root anyway, so that isn't it.
But the unavailable kernel driver makes me wonder.
aupkg02 is a z/VM Guest that will be used for that - I don't know of the specific setup details.
I know that there is work ongoing to make this more of a normal *stack setup.
We have BLK_DEV_ DM_BUILTIN= y
CONFIG_
CONFIG_BLK_DEV_DM=y
So this should always be there.
But the following executed by one who is allowed on one of the systems should help to debug: tools-0. 5.0+git1. 656f8865/ debian/ tests file-loopback
pull-lp-source multipath-tools
cd multipath-
sudo ./kpartx-
# The former should reproduce the error
# Then look why/what might be going on with /dev/mapper/control
ls -laF /dev/mapper/control
lsmod | grep dm
# check dmesg ?
# more?
I need access, help from one with access or have to wait for the new *stack systems