diskimage-builder/diskimage_builder/block_device
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
..
level0 Move localloop to exec_sudo 2018-06-29 11:22:24 +10:00
level1 Call kpartx remove in umount, not cleanup 2018-06-29 11:22:33 +10:00
level2 Convert labels to upper case 2018-06-19 11:12:54 +02:00
level3 Don't fstrim vfat partitions 2018-01-23 13:24:09 +11:00
level4 Move rollback into NodeBase object 2017-06-08 17:14:20 +10:00
tests block-device lvm: fix umount phase 2018-06-28 15:21:59 +10:00
__init__.py Clear __init__.py from cmd move 2017-05-11 18:52:14 +10:00
blockdevice.py Set default label for XFS disks 2018-01-29 15:10:08 +11:00
cmd.py Refactor: use lazy logging 2017-05-30 14:39:58 +10:00
config.py Remove redundant word 2018-06-19 18:00:11 +08:00
exception.py Move exception to it's own file (again) 2017-05-20 06:44:39 +00:00
plugin.py Move rollback into NodeBase object 2017-06-08 17:14:20 +10:00
utils.py Move localloop to exec_sudo 2018-06-29 11:22:24 +10:00