Ian Wienand f94943344f Call kpartx remove in umount, not cleanup ... Similar to I697bfbf042816c5ddf170bde9534cc4f0c7279ff, the order of things called is "dib-block-device umount" *then* "dib-block-device cleanup". Because we're doing the "kpartx -d" here in cleanup, it means that the loop-device is removed in umount phase from level0/localloop.py, then afterwards we try and remove the partitions. Change-Id: I7af3c5cf66afd81a481f454b5207af552ad52a32 TODO: a test case to ensure the ordering		2018-06-29 11:22:33 +10:00
..
__init__.py	Create and use plugin/node abstract classes	2017-05-26 11:48:11 +10:00
lvm.py	Move localloop to exec_sudo	2018-06-29 11:22:24 +10:00
mbr.py	Sync after writing partition table	2017-06-19 17:13:36 +10:00
partition.py	Call kpartx remove in umount, not cleanup	2018-06-29 11:22:33 +10:00
partitioning.py	Call kpartx remove in umount, not cleanup	2018-06-29 11:22:33 +10:00