I just wanted to bump this issue because we're now experiencing it in an
automated deployment system, and it's been open almost a year and half
with no resolution.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to vm-builder in Ubuntu.
I have even tried couple of days ago ... /usr/share/pyshared/VMBuilder/util.py
umount_cmd = [umount, -l, -t, tmpfs, mount_point ]
just tried added 'lazy umount option' - but no luck.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
Well, that workaround did not help me.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to vm-builder in Ubuntu.
https://bugs.launchpad.net/bugs/879710
Title:
ubuntu-vm-builder crashes when trying to umount tmp directory.
To manage
This bug duplicates https://bugs.launchpad.net/vmbuilder/+bug/966439 .
The workaround is to add --removepkg=cron to the vmbuilder command
line.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to vm-builder in Ubuntu.
Hi
Based on some of your comments I tried to find what was the issue with the
umount
The below command helped me to get the information who is holding the lock so
based on Serge Hallyn (serge-hallyn) request the error shows as follows, (lsof
didn't help me much here so I used fuser)
I just wanted to bump this issue as I've been experiencing it without
fail for the last two days and the posted workaround has not resolved
the issue. Currently running 11.10 x64. My command line has been:
sudo vmbuilder kvm ubuntu -v --debug --suite=lucid --flavour=virtual
--rootsize=4096
Missed the attach, should be here.
** Attachment added: vmbuilder_lsof_results_and_error_20120316.txt
https://bugs.launchpad.net/ubuntu/+source/vm-builder/+bug/879710/+attachment/2881786/+files/vmbuilder_lsof_results_and_error_20120316.txt
--
You received this bug notification because you
Wanted to add a note -- Resolved my own recurring issue by switching from lucid
to essentially any other release. Can confirm that both maverick and oneiric
work for me, having changed only the release in the call to vmbuilder.
.i.e:
sudo vmbuilder kvm ubuntu -v --debug --suite=maverick
I see this every time on one KVM host machine and never on my other KVM
host machine.
Good one is:
Fully patched 11.10 Server (no desktop) acting as KVM host using
vmbuilder to create guest instances of 11.10 server.
Bad one is:
Fully patched 11.10 Workstation with Virtualization
I added this corresponding line:
def unmount_dev(self):
self.context.cancel_cleanup(self.unmount_dev)
run_cmd('chroot', '%s' % self.context.chroot_dir,
'/etc/init.d/cron','stop') // -- HERE
run_cmd('umount', '%s/dev' % self.context.chroot_dir)
That seems to be a
I will attach the debug log vmbuilder with --addpkg ubuntu-desktop and debug
lines:
run_cmd('lsof', '%s/proc' % self.context.chroot_dir)
run_cmd('lsof', '%s/dev/pts' % self.context.chroot_dir)
run_cmd('lsof', '%s/dev' % self.context.chroot_dir)
With run_cmd('ps', '-ef') or without --addpkg
Gah! Thanks. Unfortunately my snipped was bad. That was supposed to
read:
run_cmd('ps', '-ef');
run_cmd('lsof', '%s/dev' % self.context.chroot_dir)
run_cmd('mount')
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
Ouch. I replaced the code with the new lines and ran vmbuilder twice.
Unfortunately everything worked fine this way and I couldn't reproduce
the problem again (obviosuly I removed the run_cmd('sleep', '10') fix
too).
I experienced something similar with another server, at first vmbuilder
crashed
Hm, thanks. It's also possible that the race is just so tight that the
1-2 seconds to run lsof and mount allowed it to proceed.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to vm-builder in Ubuntu.
Hey Serge, I can reproduce this and I'm using the same versions
mentioned in the bug description.
I added the three lines you suggested to /usr/lib/python2.7/dist-
packages/VMBuilder/plugins/ubuntu/dapper.py and this is what I got:
vmbuilder kvm ubuntu --suite=oneiric --flavour=virtual
Added the fix and tested. Works great!
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to vm-builder in Ubuntu.
https://bugs.launchpad.net/bugs/879710
Title:
ubuntu-vm-builder crashes when trying to umount tmp directory.
To manage
Whoever is able to reproduce this, to figure out what is keeping the device
pinned, could you replace the
run_cmd('sleep', '10');
above with
run_cmd('ps', '-ef');
run_cmd('lsof', '%s/dev')
run_cmd('mount')
and post the results here?
--
You received this bug notification because
A simple workaround is simply add some sleep as follows.
def unmount_dev(self):
self.context.cancel_cleanup(self.unmount_dev)
run_cmd('sleep', '10'); // --- add this line.
run_cmd('umount', '%s/dev' % self.context.chroot_dir)
Above
--
You received this bug
Confirmed, I was able to reproduce this error.
** Changed in: vm-builder (Ubuntu)
Importance: Undecided = Medium
** Changed in: vm-builder (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to vm-builder in Ubuntu.
https://bugs.launchpad.net/bugs/879710
Title:
ubuntu-vm-builder crashes when trying to umount tmp directory.
To manage notifications about this bug go to:
20 matches
Mail list logo
