Comment 1 for bug 1644253

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 (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
CONFIG_BLK_DEV_DM_BUILTIN=y
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:
pull-lp-source multipath-tools
cd multipath-tools-0.5.0+git1.656f8865/debian/tests
sudo ./kpartx-file-loopback
# 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