ubuntu-vm-builder crashes when trying to umount tmp directory.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
vm-builder (Ubuntu) |
Confirmed
|
Medium
|
Unassigned |
Bug Description
Description: Ubuntu 11.10
Release: 11.10
ubuntu-vm-builder:
Installed: 0.12.4+
Candidate: 0.12.4+
Version table:
*** 0.12.4+
500 http://
100 /var/lib/
I've tried creating VM 10-12 times in the last 24 hours with different configurations and I've only had it work once.
Command line:
sudo ubuntu-vm-builder kvm ubuntu --suite oneiric --flavour virtual --arch amd64 -o --libvirt qemu:///system --hostname ldaptest --bridge br0 --user shane --pass changeme --addpkg acpid --addpkg openssh-server
Error:
2011-10-21 16:38:48,590 INFO : umount: /tmp/tmpAyJUcY/dev: device is busy.
2011-10-21 16:38:48,590 INFO : (In some cases useful info about processes that use
2011-10-21 16:38:48,591 INFO : the device is found by lsof(8) or fuser(1))
2011-10-21 16:38:48,591 INFO : Cleaning up
2011-10-21 16:38:48,591 ERROR : Process (['umount', '/tmp/tmpAyJUcY
(In some cases useful info about processes that use
the device is found by lsof(8) or fuser(1))
Traceback (most recent call last):
File "/usr/bin/
uvb.main()
File "/usr/lib/
distro.
File "/usr/lib/
self.
File "/usr/lib/
call_
File "/usr/lib/
getattr(
File "/usr/lib/
self.
File "/usr/lib/
run_
File "/usr/lib/
raise VMBuilderException, "Process (%s) returned %d. stdout: %s, stderr: %s" % (args.__repr__(), status, mystdout.buf, mystderr.buf)
VMBuilder.
(In some cases useful info about processes that use
the device is found by lsof(8) or fuser(1))
ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: ubuntu-vm-builder 0.12.4+
ProcVersionSign
Uname: Linux 3.0.0-12-generic x86_64
NonfreeKernelMo
ApportVersion: 1.23-0ubuntu3
Architecture: amd64
Date: Fri Oct 21 16:39:08 2011
InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111011)
PackageArchitec
ProcEnviron:
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: vm-builder
UpgradeStatus: No upgrade log present (probably fresh install)
Confirmed, I was able to reproduce this error.