MAAS

Ephemeral environments using the wrong kernel

Bug #1656425 reported by Lee Trager on 2017-01-13

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	MAAS	Fix Released	Critical	Lee Trager	MAAS 2.2.0
	2.1	Fix Released	Critical	Lee Trager	MAAS 2.1.4

Bug Description

Intermittently the ephemeral environment booted by MAAS uses the wrong kernel. The deployed system does use the right kernel. Clearing the boot-resources on the rack(rm -rf /var/lib/maas/boot-resources/*) normally fixes the problem.

Related branches

lp:~ltrager/maas/lp1656425

Merged into lp:~maas-committers/maas/trunk at revision 5642

Gavin Panella (community): Approve on 2017-01-17

lp:~ltrager/maas/lp1656425_2.1

Merged into lp:maas/2.1 at revision 5580

Lee Trager (community): Approve on 2017-01-19

Revision history for this message

Lee Trager (ltrager) wrote on 2017-01-13:

test Edit (647 bytes, text/plain)

This appears to be a problem with how the rack controller is creating the hard links in /var/lib/maas/boot-resources/current. The attached script stops the rack, clears the boot-resources, restarts the rack, once the rack finishes checks that the ga-16.04 kernel is hard linked to the correct file using the SHA256 found in metadata stream. 32/100 times the rack controller links the ga-16.04 kernel incorrectly. I've confirmed the region is correctly downloading and serving all files.

Revision history for this message

Lee Trager (ltrager) wrote on 2017-01-14: