precise hwe install via curtin boots non-hwe kernel

Bug #1357532 reported by Jason Hobbs on 2014-08-15
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
MAAS
High
Blake Rouse
1.7
High
Blake Rouse
curtin
Undecided
Unassigned
maas-images
Undecided
Unassigned
maas (Ubuntu)
Undecided
Unassigned
Trusty
Critical
Unassigned

Bug Description

I'm trying to install precise/hwe-t to a node using the fastpath installer in maas, but the node boots with a 3.2.0-67 kernel instead of the hwe-t kernel (3.13.0-x).

root@trusty-maas4:/var/lib/maas/boot-resources/current/ubuntu/amd64/hwe-t/precise/daily# tar -ztvf root-tgz ./boot/vmlinuz*
-rw------- 0/0 4986960 2014-07-15 18:11 ./boot/vmlinuz-3.2.0-67-generic

Here's my maas.meta with version info on it.
http://paste.ubuntu.com/8056486/

Related branches

Jason Hobbs (jason-hobbs) wrote :

This also affects the hwe-s kernel.

Jason Hobbs (jason-hobbs) wrote :

Err, the hwe-s root-tgz.

Jason Hobbs (jason-hobbs) wrote :

The boot images, like boot-kernel and boot-initrd, have the correct hwe-t kernel. It's just the root-tgz that has the precise kernel.

Jason Hobbs (jason-hobbs) wrote :

smoser says it's expected to not have the hwe-t kernel in the root-tgz. curtin should be installing the hwe-t kernel during install, but that isn't working.

the reason it's not working is because the install_kernel() function in curthooks.py uses apt-cache search to find the package it wants to install. That search is failing because apt-get update has never been run, so there is no cache to search.

Andres Rodriguez (andreserl) wrote :

chroot: failed to run command 'eatmydata': No such file or directory
Unexpected error while running command.
Command: ['chroot', '/tmp/tmp75AQEC/target', 'eatmydata', 'apt-get', 'install', '--quiet', '--assume-yes', '--option=Dpkg::options::=--force-uns
afe-io', 'linux-generic-lts-trusty']
Exit code: 127

Andres Rodriguez (andreserl) wrote :

We need to figure out where to better fix this issue. I'm leaning towards including the actual hwe kernel in the root image, as this seems the less intrusive and simple.

Jason Hobbs (jason-hobbs) wrote :

The changes in this branch fix this issue and allow the hwe-t kernel to be installed with precise.

lp:~jason-hobbs/curtin/curtin-fix-lts-kernel-install

However, I think they will result in all precise installs using the hwe-t kernel.

If the hwe-t root-tgz had the hwe-t kernels in them, we would never have to install kernel packages during curtin ubuntu installs, right? That seems like the simplest approach to me.

Julian Edwards (julian-edwards) wrote :

Possibly related bugs
 - bug 1337327
 - bug 1329366

Please dupe as necessary as I don't know enough about this to do so.

Changed in maas:
status: New → Incomplete
Scott Moser (smoser) on 2014-08-19
summary: - precise hwe-t root-tgz contains precise kernel, not hwe-t kernel
+ precise hwe-t curtin install boots non hwe kernel
Scott Moser (smoser) on 2014-08-19
summary: - precise hwe-t curtin install boots non hwe kernel
+ precise hwe install via curtin boots non-hwe kernel
Blake Rouse (blake-rouse) wrote :

This is because of

if purpose == "xinstall":
        osystem = Config.objects.get_config('commissioning_osystem')
        series = Config.objects.get_config('commissioning_distro_series')

in the api/pxeconfig.py.

Changed in maas:
status: Incomplete → In Progress
importance: Undecided → High
milestone: none → 1.7.0
assignee: nobody → Blake Rouse (blake-rouse)
Blake Rouse (blake-rouse) wrote :

This does not affect curtin or maas-images.

Changed in curtin:
status: New → Invalid
Changed in maas-images:
status: New → Invalid
Changed in maas:
milestone: 1.7.0 → next
Changed in maas:
status: In Progress → Fix Committed
Christian Reis (kiko) on 2014-10-30
Changed in maas:
milestone: next → 1.7.1
Changed in maas:
milestone: 1.7.1 → none
status: Fix Committed → Fix Released
Andres Rodriguez (andreserl) wrote :

This has been tested and verified to work accordingly.

tags: added: verification-done
Changed in maas (Ubuntu):
status: New → Fix Released
Changed in maas (Ubuntu Trusty):
importance: Undecided → Critical
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package maas - 1.7.6+bzr3376-0ubuntu2~14.04.1

---------------
maas (1.7.6+bzr3376-0ubuntu2~14.04.1) trusty; urgency=medium

  * debian/control: Make maas-dns a Dependy of maas-region-controller.
  * debian/maas-region-controller.postinst: Ensure DNS config migration is
    always run. (LP: #1413388)

 -- Andres Rodriguez <email address hidden> Fri, 10 Jul 2015 13:47:40 -0400

Changed in maas (Ubuntu Trusty):
status: New → Fix Released
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