Your message dated Mon, 11 May 2026 10:49:05 -0600
with message-id <[email protected]>
and subject line Closing unreproducible, old bug
has caused the Debian Bug report #916405,
regarding vmdb2 (called from autopkgtest-build-qemu) fails to unmount loop
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
916405: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916405
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: vmdb2
Version: 0.13.2-2
Severity: important

Hi,

building a new autopkgtest image with autopkgtest-build-qemu (which uses vmdb2)
fails with the following error

root@BOTOX:/var/lib/schroot/btrfs# autopkgtest-build-qemu unstable 
/var/lib/schroot/btrfs/autopkgtest-sid-vmdb2.img 
http://debian.mirror.lrz.de/debian
Using customization script /usr/share/autopkgtest/setup-commands/setup-testbed 
...
Load spec file /tmp/tmp.g5edaZwjSn
Creating image file /var/lib/schroot/btrfs/autopkgtest-sid-vmdb2.img.raw (size 
20G)
Exec: ['qemu-img', 'create', '-f', 'raw', 
'/var/lib/schroot/btrfs/autopkgtest-sid-vmdb2.img.raw', '20G']
Creating partition table (msdos) on 
/var/lib/schroot/btrfs/autopkgtest-sid-vmdb2.img.raw
Exec: ['parted', '-s', '/var/lib/schroot/btrfs/autopkgtest-sid-vmdb2.img.raw', 
'mklabel', 'msdos']
Creating partition (primary) on 
/var/lib/schroot/btrfs/autopkgtest-sid-vmdb2.img.raw (0% to 100%)
Exec: ['parted', '-s', '/var/lib/schroot/btrfs/autopkgtest-sid-vmdb2.img.raw', 
'mkpart', 'primary', 'ext2', '0%', '100%']
Exec: ['kpartx', '-dsv', '/var/lib/schroot/btrfs/autopkgtest-sid-vmdb2.img.raw']
Exec: ['kpartx', '-asv', '/var/lib/schroot/btrfs/autopkgtest-sid-vmdb2.img.raw']
Creating ext4 filesystem on /dev/mapper/loop0p1
Exec: ['/sbin/mkfs', '-t', 'ext4', '/dev/mapper/loop0p1']
Exec: ['mount', '/dev/mapper/loop0p1', '/tmp/tmpz1biu6_9']
Debootstrap unstable /tmp/tmpz1biu6_9 http://debian.mirror.lrz.de/debian
Exec: ['debootstrap', '--variant', '-', 'unstable', '/tmp/tmpz1biu6_9', 
'http://debian.mirror.lrz.de/debian']
Exec: ['chroot', '/tmp/tmpz1biu6_9', 'apt-get', '-y', '--no-show-progress', 
'install', 'eatmydata']
Exec: ['chroot', '/tmp/tmpz1biu6_9', 'eatmydata', 'apt-get', '-y', 
'--no-show-progress', 'install', 'linux-image-amd64', 'ifupdown']
chroot /tmp/tmpz1biu6_9 to passwd --delete root useradd --home-dir /home/user 
--create-home user passwd --delete user echo host > /etc/hostname
Exec: ['chroot', '/tmp/tmpz1biu6_9', 'sh', '-c', 'passwd --delete root\nuseradd 
--home-dir /home/user --create-home user\npasswd --delete user\necho host > 
/etc/hostname']
Installing GRUB for BIOS
Exec: ['mount', '--bind', '/dev', '/tmp/tmpz1biu6_9/dev']
Exec: ['mount', '--bind', '/proc', '/tmp/tmpz1biu6_9/proc']
Exec: ['mount', '--bind', '/sys', '/tmp/tmpz1biu6_9/sys']
Install grub-pc in chroot /tmp/tmpz1biu6_9
Exec: ['chroot', '/tmp/tmpz1biu6_9', 'apt-get', '-y', '--no-show-progress', 
'install', 'grub-pc']
Exec: ['chroot', '/tmp/tmpz1biu6_9', 'grub-mkconfig', '-o', 
'/boot/grub/grub.cfg']
Exec: ['chroot', '/tmp/tmpz1biu6_9', 'grub-install', '--target=i386-pc', 
'--no-nvram', '--force-extra-removable', '--no-floppy', '--modules=part_msdos 
part_gpt', '--grub-mkdevicemap=/boot/grub/device.map', '/dev/loop0']
Exec: ['umount', '/tmp/tmpz1biu6_9/dev']
Exec: ['umount', '/tmp/tmpz1biu6_9/proc']
Exec: ['umount', '/tmp/tmpz1biu6_9/sys']
ERROR: Command failed: umount /tmp/tmpz1biu6_9/sys
b''
b'umount: /tmp/tmpz1biu6_9/sys: target is busy.\n'
Something went wrong, cleaning up!
Exec: ['umount', '/tmp/tmpz1biu6_9']
ERROR: Command failed: umount /tmp/tmpz1biu6_9
b''
b'umount: /tmp/tmpz1biu6_9: target is busy.\n'
Undoing loopback devices for partitions on 
/var/lib/schroot/btrfs/autopkgtest-sid-vmdb2.img.raw
Exec: ['kpartx', '-dsv', '/var/lib/schroot/btrfs/autopkgtest-sid-vmdb2.img.raw']
ERROR: Command failed: kpartx -dsv 
/var/lib/schroot/btrfs/autopkgtest-sid-vmdb2.img.raw
b'loop0p1 is in use. Not removing'
b'loop deleted : /dev/loop0\n'

I have no exact idea why, but the culprit is a mount of
/tmp/tmpz1biu6_9/sys/fs/fuse/connections that is not visible anywhere.  I
could not see it in mount, but autocompletion of umount
/tmp/tmpz1biu6_9/sys/<TAB> showed it. After umount I was able to unmount
/tmp/.../sys and finally /tmp/tmp...

Bernhard


-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (900, 'testing'), (500, 'stable'), (400, 'unstable'), (1, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.18.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE= 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages vmdb2 depends on:
ii  cmdtest         0.32-2
ii  debootstrap     1.0.111
ii  kpartx          0.7.9-1
ii  parted          3.2-23
ii  python3         3.6.7-1
ii  python3-cliapp  1.20180812.1-2
ii  python3-jinja2  2.10-1
ii  python3-yaml    3.13-1

Versions of packages vmdb2 recommends:
ii  ansible  2.7.1+dfsg-2

vmdb2 suggests no packages.

-- no debconf information

--- End Message ---
--- Begin Message ---
This bug was opened in December 2018. The upstream author (and then
maintainer) asked for confirmation on the bug in mid-2020. No further
interaction was recorded.

I'm closing this bug. If you find this to be incorrect, please reopen.

Attachment: signature.asc
Description: PGP signature


--- End Message ---

Reply via email to