python-vm-builder-0.12.4+bzr462-0ubuntu1: swap partitions fail to be created properly when "lucid" is the target
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
vm-builder (Ubuntu) |
Confirmed
|
Low
|
Unassigned |
Bug Description
I am using version 0.12.4+
During build, I see this in the build log:
2011-02-28 15:36:01,700 INFO : Adding type 3 partition to disk image: /tmp/tmpnFjJJ2
2011-02-28 15:36:01,707 INFO : [0] ../../libparted
2011-02-28 15:36:01,713 INFO : Creating loop devices corresponding to the created partitions
2011-02-28 15:36:01,721 INFO : Creating file systems
2011-02-28 15:36:01,833 INFO : mke2fs 1.41.14 (22-Dec-2010)
2011-02-28 15:36:14,592 INFO : mkswap: /dev/mapper/
2011-02-28 15:36:14,592 INFO : on whole disk. Use -f to force.
At the end of the build log, there is a traceback:
2011-02-28 15:39:44,643 INFO : Unmounting tmpfs from /tmp/tmp1TErm0tmpfs
2011-02-28 15:39:44,650 INFO : umount: /tmp/tmp1TErm0t
2011-02-28 15:39:44,650 INFO : (In some cases useful info about processes that use
2011-02-28 15:39:44,650 INFO : the device is found by lsof(8) or fuser(1))
Traceback (most recent call last):
File "/usr/bin/
cli.main()
File "/usr/lib/
util.
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))
None of this happens when I do not specify a swap partition. This also doesn't happen when I build a hardy machine (I've only tried hardy and lucid as targets)
Once you boot the machine, you will see this message:
The disk drive for /dev/sda2 is not ready yet or not present
Continue to wait; or Press S to skip mounting or M for manual recovery
Let me know if you need any further information!
Changed in vm-builder (Ubuntu): | |
status: | New → Confirmed |
Hi Randy,
Thank you for reporting bugs and trying to make Ubuntu Server better!
Could you please provide a Step by step to be able to reproduce this bug. Once we can reproduce this bug we'll investigate further and maybe ask for more information.
I'm marking this bug as incomplete until the information requested is provided.
Best regards,