Unable to commission node which needs hwe kernel on trusty

Bug #1464866 reported by Darryl Weaver on 2015-06-13
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
maas-images
Undecided
Unassigned

Bug Description

Using a Dell certified system (R430) with an Intel 10GbE X710 NIC needs the point release kernel from 14.04.2 to work correctly.
Starting the server from a 14.04.2 USB stick, the NIC is working correctly.

In MAAS this is unable to enlist or commission.
When trying to enlist or if adding the node manually and trying to commission, the NIC is not working from the 14.04 MAAS boot kernel, which is only kernel 3.13.0-35-generic.

If enabling the architecture to be a later hwe kernel, there is no trusty support available for commissioning and no ability to select utopic or vivid for commissioning in the first place and so nodes cannot be used with MAAS.

This should probably be related to bug #1454024 and bug #1443644.

This was tested on maas-1.7.4+bzr3366-0ubuntu.

To re-create:
1 enlist a node to MAAS either manually or automatically
2 edit the node and change the architecture to amd64/hwe-v
3 commission the node

Result:
Node fails to find boot kernel as it is trying to load amd64/hwe-v/trusty/ which does not exist.

Darryl Weaver (dweaver) wrote :

This actually looks like a mistake in the simplestreams service providing boot images to MAAS.
The json file lists later hardware enabled kernels for precise, but not for trusty.

For example, the contents of the URL http://maas.ubuntu.com/images/ephemeral-v2/releases/streams/v1/index.json includes:
    "com.ubuntu.maas:v2:boot:12.04:amd64:hwe-p",
    "com.ubuntu.maas:v2:boot:12.04:amd64:hwe-q",
    "com.ubuntu.maas:v2:boot:12.04:amd64:hwe-r",
    "com.ubuntu.maas:v2:boot:12.04:amd64:hwe-s",
    "com.ubuntu.maas:v2:boot:12.04:amd64:hwe-t",
...
    "com.ubuntu.maas:v2:boot:14.04:amd64:hwe-t",

Precise has hwe kernels up to trusty enabled.
Trusty has no hwe kernels and can only deploy the hwe-t kernel.

Darryl Weaver (dweaver) wrote :

Confirmed, as this is different to the daily simplestreams version, which includes all the hwe enabled kernels.
i.e. the contents of URL: http://maas.ubuntu.com/images/ephemeral-v2/daily/streams/v1/index.json contains:

    "com.ubuntu.maas.daily:v2:boot:12.04:amd64:hwe-p",
    "com.ubuntu.maas.daily:v2:boot:12.04:amd64:hwe-q",
    "com.ubuntu.maas.daily:v2:boot:12.04:amd64:hwe-r",
    "com.ubuntu.maas.daily:v2:boot:12.04:amd64:hwe-s",
    "com.ubuntu.maas.daily:v2:boot:12.04:amd64:hwe-t",
..
    "com.ubuntu.maas.daily:v2:boot:14.04:amd64:hwe-t",
    "com.ubuntu.maas.daily:v2:boot:14.04:amd64:hwe-u",
    "com.ubuntu.maas.daily:v2:boot:14.04:amd64:hwe-v",

Please add 14.04 hwe kernels to the released streams.

Raphaël Badin (rvb) wrote :

Well sleuthed. What you experience is indeed a combination of a problem in the available images plus bug 1454024.

no longer affects: maas
Darryl Weaver (dweaver) wrote :

Also see bug #1465071 as the trusty hwe-v kernel panics on boot.
So, that bug needs fixing before publishing into released.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers