MAAS 3.5 Problems with in-memory booting of Custom OSes

Users
1

I am attempting to boot a Rocky 8 custom image using the new ‘Deploy in memory’ option of MaaS 3.5 ( installed via snap using ‘3.5/stable’) but it seems the only OSes I can get to work like that are the non-custom Ubuntu ones.

I used the packer-maas project to build the custom image and uploaded it to MaaS via the following command:

maas pnx boot-resources create name="custom/rocky8" \
  title="Rocky 8" architecture='amd64/generic' \
  base_image='rhel/8' filetype='tgz' \
  content@=rocky8.tar.gz

The custom image deploys onto a system in the ‘traditional’ manner without issue.

Encountered errors in the logs are:

Marking node failed - Missing boot image rhel/amd64/generic/8.

The deployed system just drops into what looks like a busybox shell and just sits there till I power off the VM.

2

Could you please open a bug on launchpad?

3

I’ll get a new bug report opened up and link it back here.

4

Searched through the bug reports and spotted one that looks pretty similar to the issue I hit

Before I cut a new one I’m going to double check I’m working on the same release (or greater) that is mentioned in that bug report.

5

Verified I’m using a newer version than the version reported in the above bug report.

6

Bug report submitted: Bug #2075555 “Custom OSes fail to deploy 'in memory'” : Bugs : MAAS

7

Hi @quinn. Thank you for the bug report. I was able to reproduce it on my local environment. Let’s continue the discussion to the bug itself.

8

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.