Rescue fails on maas 2.3.6/2.3.5 with boot-kernel failed no such file or directory

[Steven Parker]

I ran into this and wanted to register a workaround.

So if you deploy cloud with earlier ubuntu version and then upgrade the node later you may have issues using maas to enter rescue mode.

Replicate with:

Install xenial series via maas then upgrade node to bionic.
Change commission and deploy options to bionic.

Try and rescue node.

You should get failure to boot in rescue mode.
  loading ubuntu/amd64/ga-16.04/bionic/daily/boot-kernel failed no such file or directory.

  16.04/bionic is not a valid series. It looks like it is now a mix between xenial (16.04 and bionic)

Workaround:

Fix by reverting commission and deployment versions back to xenial. You can then rescue the node with xenial.

Feel free to close bug as this is a very old version of maas.

[Alberto Donato (ack)]

I can't reproduce this with current maas.

Entering rescue mode uses the same release kernel as currently in use by the deployed machine.

Do you still see this issue with latest maas version?

[Launchpad Janitor (janitor)]

[Expired for MAAS because there has been no activity for 60 days.]