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
..
block_device	Call kpartx remove in umount, not cleanup	2018-06-29 11:22:33 +10:00
elements	Add iscsi-boot element for CentOS images	2018-06-25 12:01:52 +00:00
lib	Save and close stdout on exit	2018-05-25 11:48:20 +10:00
tests	Fail if two elements provide the same thing	2018-02-23 10:04:26 +11:00
__init__.py	Bump hacking to 0.9.x series	2014-07-21 10:15:41 +02:00
disk_image_create.py	squash-package-install to use the correct python	2017-03-13 20:24:39 +11:00
element_dependencies.py	Fail if two elements provide the same thing	2018-02-23 10:04:26 +11:00
logging_config.py	Add timestamp output filter	2017-06-16 15:58:50 +10:00
paths.py	Move diskimage-image-create to an entry point	2016-11-02 05:12:11 +00:00
version.py	Create docs site containing element READMEs	2015-02-10 11:45:35 -08:00