* Fix the orphaned loop dev created by kpartx -u

[fmg-stephen-martin]

Since updating to 14.9.3 from 14.9.0, we've had issues with an orphaned loop device (and a number of superfluous drive mounts) being left behind after each OS build. This issue only occurred when a project installed grub on a hardrive. I.e. <grub-install />

We've tracked the issue down to the losetup method in the grubinstaller_base class:

• The method creates a loop device attached to the disk image
• It then calls kpartx -u against the same disk image. This results in a second loop device being created, that is not tracked or cleaned up at all

Instead, calling kpartx -u against the loop device already attached to file image fixes this issue.

[t-8ch]

Thanks for the patch!

Couldn't we add --partscan to the initial call to losetup for the same effect? That would feel nicer to me.

[t-8ch]

Hi @fmg-stephen-martin any feedback to the proposed approach?

[t-8ch]

This should be fixed by 1330249e6d02691134d98a3c5509c60f74710cae .