Ubuntu
linux package

  1. Bug #1898808
  2. Comment #36

Comment 36 for bug 1898808

Revision history for this message
Jeff Lane  (bladernr) wrote : Re: [maas][focal]unable to deploy 20.04(focal) w/ default kernel for sut after images update on Oct 5

Thanks Lee... I think there are two different issues that need to be resolved.

First, is that we recently introduced patches to the 5.4 kernel for Intel x710 NICs because 5.4 only saw some of the NIC ports. So to solve that problem, we would need new maas images spun that include the latest 5.4 kernel SRU for the boot-kernel and boot-initrd, so that MAAS deployments will succeed on systems that use the Intel X710 LOM.

Second, is this issue. The two look similar at first, BUT, as Alec reported, after Oct 5, focal deployments that DID work are now not working. And looking at the images on maas.io, the most recent focal ones were from Oct 5, which would hint to me that something broke in that image update.

Lee, I wonder¸ is there a way for them to download the older images from here:
 http://images.maas.io/ephemeral-v3/stable/focal/amd64/20200930/ga-20.04/generic/

to see if restoring the older maas images and boot media resolves the issue?

I looked on one of my MAAS servers and it has only the Oct 5 update, and on another MAAS server, it only has the Sept 30 update. So am I correct in thinking that downloading that media to a new subdirectory in /var/lib/maas/boot-resources and then pointing the "current" symlink to that older media would allow them to boot using the older Sept 30 kernel and initrd?

Just curious if that would work. If for no other reason than to verify that indeed the breakage is in the Oct 5 images as a sort of bisect.