[Bug 1543430] Re: kpartx 0.5.0-7ubuntu11 fails to remove loop mapping on kpartx -d

[Dimitri John Ledkov]

Well, it's a problem on s390x, where they are not dedicated VMs.

wgrant has run a cleanup of loopsetup devices now, on those builders.

adding a check to test that losetup -f matches after a kpartx -a / -d
round trip.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to multipath-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1543430

Title:
  kpartx 0.5.0-7ubuntu11 fails to remove loop mapping on kpartx -d

Status in multipath-tools package in Ubuntu:
  New

Bug description:
  I've observed in livefs build logs that with kpartx 0.5.0-7ubuntu12,
  'kpartx -d' is not removing the loop mapping (losetup -d).  E.g.,
  build log diff:

   + kpartx -v -d binary/boot/disk.ext4
   del devmap : loop0p1
  -loop deleted : /dev/loop0

  This doesn't seem to be causing any immediate practical problems
  because each livefs build gets a dedicated VM which is torn down
  afterwards, so the mappings do not persist.  But it's definitely
  incorrect for these mappings to persist.

  The good build log used kpartx 0.5.0-7ubuntu9.  Testing the
  intermediate versions, 0.5.0-7ubuntu11 shows the same buggy behavior
  as 12.  10 clears the loop mapping, but also appears to fail to
  correctly set up partitions in my test case so I'm not sure if this
  bug is present or not in 0.5.0-7ubuntu10.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1543430/+subscriptions