Can't build a raring VM

Bug #1174148 reported by I_Am on 2013-04-29
44
This bug affects 9 people
Affects Status Importance Assigned to Milestone
vm-builder (Ubuntu)
High
Serge Hallyn
Precise
High
Unassigned
Quantal
High
Unassigned
Raring
High
Unassigned

Bug Description

=================================
SRU Justification:
1. Impact: cannot build vms for raring
2. Development fix: add raring and saucy as valid suites
3. Stable fix: same as development fix
4. test case:
   sudo vm-builder kvm ubuntu --suite raring
5. regression potential: this only introduces new classes to support the new suites, so should not regress any of the previously supported suites.
=================================

If you try and build a raring vm on raring, it fails. Should be an easy fix, but is pretty important.

root@main:~# ubuntu-vm-builder kvm raring
2013-04-29 00:42:38,745 INFO : Calling hook: preflight_check
2013-04-29 00:42:38,745 INFO : Cleaning up
2013-04-29 00:42:38,745 ERROR : Invalid suite: "raring". Valid suites are: dapper gutsy hardy intrepid jaunty karmic lucid maverick natty oneiric precise quantal
Traceback (most recent call last):
  File "/usr/bin/ubuntu-vm-builder", line 24, in <module>
    uvb.main()
  File "/usr/lib/python2.7/dist-packages/VMBuilder/contrib/cli.py", line 218, in main
    distro.build_chroot()
  File "/usr/lib/python2.7/dist-packages/VMBuilder/distro.py", line 81, in build_chroot
    self.call_hooks('preflight_check')
  File "/usr/lib/python2.7/dist-packages/VMBuilder/distro.py", line 67, in call_hooks
    call_hooks(self, *args, **kwargs)
  File "/usr/lib/python2.7/dist-packages/VMBuilder/util.py", line 165, in call_hooks
    getattr(context, func, log_no_such_method)(*args, **kwargs)
  File "/usr/lib/python2.7/dist-packages/VMBuilder/plugins/ubuntu/distro.py", line 101, in preflight_check
    raise VMBuilderUserError('Invalid suite: "%s". Valid suites are: %s' % (suite, ' '.join(self.suites)))
VMBuilder.exception.VMBuilderUserError: Invalid suite: "raring". Valid suites are: dapper gutsy hardy intrepid jaunty karmic lucid maverick natty oneiric precise quantal

I_Am (ionstorm66) wrote :

Copied /usr/share/pyshared/VMBuilder/plugins/ubuntu/quantal.py to /usr/share/pyshared/VMBuilder/plugins/ubuntu/raring.py

Then replaced quantal with raring inside raring.py

After that I linked /usr/share/pyshared/VMBuilder/plugins/ubuntu/raring.py to /usr/lib/python2.7/dist-packages/VMBuilder/plugins/ubuntu/raring.py

That seamed to work, but I encounter Bug #1037607. I added --addpkg linux-image-generic to my command line, and the machine build and ran fine.

marcolino (mas-marco) wrote :

You must add also ", 'raring'" , just after "'quantal'" at line 33 in /usr/share/pyshared/VMBuilder/plugins/ubuntu/distro.py

Changed in vm-builder (Ubuntu):
assignee: nobody → Serge Hallyn (serge-hallyn)
importance: Undecided → High
status: New → In Progress
description: updated
Changed in vm-builder (Ubuntu Precise):
importance: Undecided → High
status: New → Triaged
Changed in vm-builder (Ubuntu Raring):
importance: Undecided → High
status: New → Triaged
Changed in vm-builder (Ubuntu Quantal):
importance: Undecided → High
status: New → Triaged
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package vm-builder - 0.12.4+bzr487-0ubuntu1

---------------
vm-builder (0.12.4+bzr487-0ubuntu1) saucy; urgency=low

  * Add raring and saucy to valid ubuntu suites. (LP: #1174148)
 -- Serge Hallyn <email address hidden> Mon, 29 Apr 2013 11:13:08 -0500

Changed in vm-builder (Ubuntu):
status: In Progress → Fix Released

Hello I_Am, or anyone else affected,

Accepted vm-builder into raring-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/vm-builder/0.12.4+bzr482-0ubuntu2 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Changed in vm-builder (Ubuntu Raring):
status: Triaged → Fix Committed
tags: added: verification-needed
Changed in vm-builder (Ubuntu Quantal):
status: Triaged → Fix Committed
Brian Murray (brian-murray) wrote :

Hello I_Am, or anyone else affected,

Accepted vm-builder into quantal-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/vm-builder/0.12.4+bzr481-0ubuntu2 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Changed in vm-builder (Ubuntu Precise):
status: Triaged → Fix Committed
Brian Murray (brian-murray) wrote :

Hello I_Am, or anyone else affected,

Accepted vm-builder into precise-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/vm-builder/0.12.4+bzr477-0ubuntu4 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Joeri Verdeyen (5-info-4) wrote :

I had to symlinks /usr/share/debootstrap/scripts/gutsy to /usr/share/debootstrap/scripts/raring

Will Bryant (will-bryant-gmail) wrote :

I've tried python-vm-builder 0.12.4+bzr477-0ubuntu3. It has the necessary files to build raring VMs and they look fine to me.

Actually building a raring VM didn't work on the host I was trying it on. I'm not sure if it's an issue with python-vm-builder, but I got the following when it died:

 ** [out :: host-nwtn11] (Reading database ... 15293 files and directories currently installed.)
 ** [out :: host-nwtn11] Unpacking linux-image-3.8.0-25-generic (from .../linux-image-3.8.0-25-generic_3.8.0-25.37_amd64.deb) ...
 ** [out :: host-nwtn11] Selecting previously unselected package linux-image-virtual.
 ** [out :: host-nwtn11] Unpacking linux-image-virtual (from .../linux-image-virtual_3.8.0.25.43_amd64.deb) ...
 ** [out :: host-nwtn11]
 ** [out :: host-nwtn11] , stderr: grep: /proc/cpuinfo: No such file or directory
 ** [out :: host-nwtn11] This kernel does not support a non-PAE CPU.
 ** [out :: host-nwtn11] dpkg: error processing /var/cache/apt/archives/linux-image-3.8.0-25-generic_3.8.0-25.37_amd64.deb (--unpack):

There were other errors earlier in the VM build that may or may not be relevant (attached).

Will Bryant (will-bryant-gmail) wrote :

Ah, the above issue is LP #1037607, I'll comment there.

If I workaround using --addpkg linux-image-generic, the raring build works with the proposed python-vm-builder version, so this version looks good to release in the meantime.

Brian Murray (brian-murray) wrote :

@Will - the version number you mentioned, 0.12.4+bzr477-0ubuntu3, is no the one needing SRU verification. Was that a typo?

Unfortunately I'd reset my test env so I couldn't go back and check, but I just tried another VM rebuild using 0.12.4+bzr477-0ubuntu4 and it worked fine.

Nick Maslov (azpekt) wrote :

Hi, can anyone build Saucy (13.10) with this script? I followed recipes from first two comments - can build Raring, but not Saucy.

I`m on 13.04, will try this on 13.10.

Thanks,
NM

JJMerelo (jjmerelo) wrote :

The saucy.py and raring.py are not included, at least in the .482 version that is distributed with the python-vm-builder package in 13.04

tags: added: verification-done-precise
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package vm-builder - 0.12.4+bzr477-0ubuntu4

---------------
vm-builder (0.12.4+bzr477-0ubuntu4) precise-proposed; urgency=low

  * Add quantal, raring, and saucy to valid ubuntu suites. (LP: #1174148)
 -- Serge Hallyn <email address hidden> Mon, 29 Apr 2013 11:40:48 -0500

Changed in vm-builder (Ubuntu Precise):
status: Fix Committed → Fix Released
Changed in vm-builder (Ubuntu Raring):
status: Fix Committed → Won't Fix
Rolf Leggewie (r0lf) wrote :

quantal has seen the end of its life and is no longer receiving any updates. Marking the quantal task for this ticket as "Won't Fix".

Changed in vm-builder (Ubuntu Quantal):
status: Fix Committed → Won't Fix
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers