Creating ubuntu guest fails on extracting adduser from vm-builder
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
vm-builder (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
When running the command
ubuntu-vm-builder kvm ubuntu --suite=precise --flavour=virtual --arch=amd64 --libvirt=
I always recieve a failure on extracting files, I have tried multiple mirrors and removed the tmp files. To test this wasn't a box failure I installed a new box (same hardware specs) and same error happened. The download and verify both pass without any errors but the extract fails.
<<snip>>
I: Chosen extractor for .deb packages: dpkg-deb
I: Extracting adduser...
I: Extracting base-files...
I: Extracting base-passwd...
I: Extracting bash...
I: Extracting bsdutils...
I: Extracting busybox-
I: Extracting coreutils...
I: Extracting cpio...
I: Extracting dash...
I: Extracting debconf...
I: Extracting debianutils...
I: Extracting diffutils...
I: Extracting dpkg...
I: Extracting e2fslibs...
, stderr:
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_cmd(*cmd, **kwargs)
File "/usr/lib/
raise VMBuilderException, "Process (%s) returned %d. stdout: %s, stderr: %s" % (args.__repr__(), status, mystdout.buf, mystderr.buf)
VMBuilder.
I: Retrieving Release.gpg
I: Checking Release signature
I: Valid Release signature (key id 630239CC130E1A7
<<snip>>
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: ubuntu-vm-builder 0.12.4+
ProcVersionSign
Uname: Linux 3.2.0-38-generic x86_64
ApportVersion: 2.0.1-0ubuntu17.1
Architecture: amd64
Date: Thu Mar 14 15:18:29 2013
InstallationMedia: Ubuntu-Server 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120817.3)
MarkForUpload: True
PackageArchitec
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: vm-builder
UpgradeStatus: No upgrade log present (probably fresh install)
Status changed to 'Confirmed' because the bug affects multiple users.