diskimage-builder/elements/redhat-common/bin
Pino Toscano 626ca9ad47 Run udevadm settle after kpartx -l
it may happen that if the system where disk-image-create runs is busy,
then the kpartx -l run may leave a stale autodelete loop device.

This is because kpartx -l first adds a new loop device, then does the
listing and removes the loop device. The latter may not end before the
end of the kpartx run, leaving a loop device marked as autodelete.
Such kind of loop device will automatically delete itself, so the
 rm -r $WORKING
after
 sudo umount -f $WORKING/mnt
in the EXIT trap will fail because $WORKING does not exist anymore.

To prevent this situation, just ask udev to finish its operations,
properly removing the (temporary) loop device.

Change-Id: I12246f3dbe6b5669e698767682a5a142f803823b
2015-03-23 10:38:21 +01:00
..
extract-image Run udevadm settle after kpartx -l 2015-03-23 10:38:21 +01:00
map-packages redhat-common: Fix MariaDB-Galera-server case 2015-03-17 10:56:01 +01:00
map-services Add deprecation warning when using map-services 2014-11-12 17:03:49 +00:00