This bug was fixed in the package vm-builder - 0.12.4+bzr477-0ubuntu5
---
vm-builder (0.12.4+bzr477-0ubuntu5) precise-proposed; urgency=medium
* Add trusty to the list of valid ubuntu suites. (LP: #1287943)
-- Serge HallynTue, 04 Mar 2014 16:52:51 -0600
** Changed in: vm-buil
** Changed in: vm-builder (Ubuntu Saucy)
Status: Fix Committed => Invalid
--
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/1287943
Title:
vm-builder needs trusty suite
To m
** Tags removed: verification-needed
** Tags added: verification-needed-saucy
--
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/1287943
Title:
vm-builder needs trusty suite
To mana
It is working perfectly for me (Precise)
** Tags removed: verification-failed-precise
** Tags added: verification-done-precise
--
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/128794
Jonathon, which version of the package did you use?
--
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/1287943
Title:
vm-builder needs trusty suite
To manage notifications about thi
For me the problem was solved by updating python-vmbuilder to the latest
version.
--
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/1287943
Title:
vm-builder needs trusty suite
To
The race condition in comment #17 is only true if mystdout.closed can
become True asynchronously before we have called mystdout.close(). I'm
not sure if there's any possibility of that.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to vm
I have raised these:
Bug #1332155: debootstrap launches spurious udevd --daemon
Bug #1332165: udevd --daemon does not close stdout
--
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/12
Please open a new bug against debootstraph for this, clearly specifying
your release and any ppa's (like cloud archive) you have enabled. I
believe this was fixed by the 1.0.52 version, which we can SRU back to
precise if needed.
--
You received this bug notification because you are a member of
OK, I found it.
During debootstrap run, a process "udevd --daemon" is started. It
persists when debootstrap gets to the end. If you kill it, the process
reading from debootstrap's stdout is able to terminate.
My guess is that stdout is being passed to that daemon, and it's holding
it open.
No id
Argh. Scrub what I said about python. I can reproduce without python!
# /usr/sbin/debootstrap --arch=i386 trusty /tmp/tmpBQAxhc
http://archive.ubuntu.com/ubuntu | strace cat >db.out
...
read(0, "I: Configuring initramfs-tools.."..., 32768) = 34
write(1, "I: Configuring initramfs-tools.."..., 34)
FYI: the system I'm using has kernel 3.8.0-42-generic, i.e. it was
installed at the time when the "raring enablement stack" was active.
I can now reproduce with just a few lines:
---
import subprocess
args = ['/usr/sbin/debootstrap', '--arch=i386', 'trusty', '/tmp/tmpBQAxhc',
'http://archive.ub
I can replicate this issue with a standalone python script.
http://pastebin.com/vTREYc9n
It hangs at:
read stdout: 'I: Base system installed successfully.\n'
Furthermore, if I add a timeout to select and force it to read anyway, I
get an IOError:
read stdout: [Errno 11] Resource temporarily unav
There is a nasty race condition in the code, which is easily fixed:
--- /usr/share/pyshared/VMBuilder/util.py.orig 2010-06-10 17:20:58.0
+
+++ /usr/share/pyshared/VMBuilder/util.py 2014-06-19 10:57:09.723017475
+
@@ -108,9 +108,12 @@
mystdout = NonBlockingFile(proc.st
I see hang at "Base system installed successfully" too, building Trusty
VM under Precise 64-bit.
Last three lines of ps auxwww are:
root 20430 0.1 0.0 40060 9716 pts/2S+ 10:36 0:00
/usr/bin/python /usr/bin/vmbuilder kvm ubuntu --suite trusty --hostname trusty
--mem 512 --debug -
Same as the others are seeing for trusty.
--
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/1287943
Title:
vm-builder needs trusty suite
To manage notifications about this bug go t
Correction, not the same, but:
^CTraceback (most recent call last):
File "/usr/bin/vmbuilder", line 24, in
cli.main()
File "/usr/lib/python2.7/dist-packages/VMBuilder/contrib/cli.py", line 216,
in main
distro.build_chroot()
File "/usr/lib/python2.7/dist-packages/VMBuilder/distro.py
I did some searching around the bug tracker + google and couldn't find
anything. This is my first time poking around the bug tracker here
though, so it is possible I missed a report.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to vm-bu
Well then, that seems independent of the SRU then. Could you check and
see if there is an existing bug report about vm-builder failing to build
Saucy and if there isn't report one and mention it here? Thanks!
--
You received this bug notification because you are a member of Ubuntu
Server Team, w
I am seeing the same problem when I try with saucy.
--
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/1287943
Title:
vm-builder needs trusty suite
To manage notifications about thi
** Changed in: vm-builder (Ubuntu Precise)
Assignee: Bartosz Kosiorek (gang65) => (unassigned)
--
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/1287943
Title:
vm-builder needs
Did you get the same error trying to build a saucy system?
--
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/1287943
Title:
vm-builder needs trusty suite
To manage notifications ab
** Tags removed: verification-done-precise
** Tags added: verification-failed-precise
--
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/1287943
Title:
vm-builder needs trusty suite
I'm seeing the same error as Johan. Running 0.12.4+bzr477-0ubuntu5 on
precise (64 bits)
--
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/1287943
Title:
vm-builder needs trusty suit
Tested 0.12.4+bzr477-0ubuntu5 on precise (64 bits) did not work for me.
It stalls on:
2014-04-30 09:22:56,349 DEBUG : I: Configuring ubuntu-minimal...
2014-04-30 09:22:56,350 DEBUG : I: Configuring libc-bin...
2014-04-30 09:22:56,368 DEBUG : I: Configuring initramfs-tools...
2014-04-30 0
** Tags added: verification-done-precise
** Changed in: vm-builder (Ubuntu Precise)
Assignee: (unassigned) => Bartosz Kosiorek (gang65)
--
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.n
Hi Amir,
please open a new bug for the crash you are seeing. Indeed
revno should be an int not str in vcsersion.py
--
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/1287943
Title:
Thanks Brian, updating to proposed sources (vmbuilder version
0.12.4.r475) solved the problem for me on precise.
Meanwhile, in this revision, when calling vmbuilder --version, a python
error is raised. The cause is that 'revno' returned by the
VMBuilder.get_version_info is of type str, not int.
V
Hi Beltran,
Which release are you doing this on? Trusty vm builds fine for me on
trusty.
--
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/1287943
Title:
vm-builder needs trusty s
In addition to the files, it seems it is also necessary to mount /proc
before installing the kernel for Saucy or Trusty.
/usr/share/pyshared/VMBuilder/plugins/ubuntu/dapper.py
@@ -300,7 +300,9 @@
return (mirror, updates_mirror, security_mirror)
def install_kernel(self, destdir):
+
** Branch linked: lp:ubuntu/precise-proposed/vm-builder
** Branch linked: lp:ubuntu/saucy-proposed/vm-builder
--
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/1287943
Title:
vm-bu
Hello Chris, or anyone else affected,
Accepted vm-builder into saucy-proposed. The package will build now and
be available at http://launchpad.net/ubuntu/+source/vm-
builder/0.12.4+bzr488-0ubuntu1.13.10.1 in a few hours, and then in the
-proposed repository.
Please help us by testing this new pac
** Changed in: vm-builder (Ubuntu)
Status: In Progress => Fix Released
** Changed in: vm-builder (Ubuntu Precise)
Status: New => Triaged
** Changed in: vm-builder (Ubuntu Saucy)
Status: New => Triaged
** Changed in: vm-builder (Ubuntu Precise)
Importance: Undecided => Hig
** Changed in: vmbuilder
Assignee: Chris J Arges (arges) => (unassigned)
** Changed in: vm-builder (Ubuntu)
Assignee: Chris J Arges (arges) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to vm-builder in Ubuntu.
Thanks for submitting this bug.
** Changed in: vm-builder (Ubuntu)
Importance: Undecided => High
** Changed in: vm-builder (Ubuntu)
Status: New => In Progress
** Also affects: vm-builder (Ubuntu Precise)
Importance: Undecided
Status: New
** Also affects: vm-builder (Ubuntu S
** Description changed:
+ [Impact]
When using vm-builder it should be able to specify 'trusty' as a suite.
+
+ [Test Case]
+ sudo vmbuilder kvm ubuntu --suite trusty
+
+ [Regression Potential]
+ This just adds another release name.
** Also affects: vmbuilder
Importance: Undecided
St
36 matches
Mail list logo
