hey @westhusing
I am currently doing the same task with a similar issue, if not the same.
I am just going to hijack your thread in the hopes that we both get increased visibility and at one point will be able to write a solid answer on how simply pack and autoprovision openSUSE images with packer for MAAS.
I am currently building different custom images with HashiCorps packer 1.9.2.
Building on Ubuntu 22.04 works so far.
I used the SLES15 template from the official git repositories.
https://github.com/canonical/packer-maas
Instead of the SLES15 ISO I decided to use OpenSuse Leap 15.4.
This requires some editing of the autoyast file in the http subfolder (see readme). The one provided comes with modules and reference for SLES and some closed sources. After editing this, I was able to create a successful build. Import into maas via API works, too.
When deploying after the first reboot, I am left with this
I tried to create that folder and copy contents from similar folders in to the one mentioned in the screenshot (there is also a boot-tgz in a suse15 folder somewhere else (generic) that I placed on this location, too) but so far it made no difference.
I would be generally grateful if some can point me in a general direction how to resolve this.
My next approach will be to use an existing openSUSE installation, have an autoyast created from that, then rebuild, then try another deploy. I can’t say what causes the issue, yet.
I will also try to build a centOs8-stream custom stock images and see if I can get that to deploy.
I am on maasserver MAAS : 3.4.0~rc1, snap version.
I read somewhere that a snap permission issue existed in the past, that blocked access to the folder structure for some applications relevant for this process. But I am not sure if this is still relevant here.
Also, I will have to look further into the topic of tags. I guess this to be boot kernel related (please correct me if I am wrong) and thought the right kernel parameters via tags could help.
Edit:
The command I used to import my openSUSE custom image
maas admin boot-resources create name='custom/suse15' title='suse15' architecture='amd64/generic' filetype='tgz' content@=sles15.tar.gz
I just saw in another thread a more complex boot resource command.
I will give it a try tomorrow. Maybe I am “just” missing some parameters.
https://discourse.maas.io/t/proposed-improvements-for-custom-image-handling-in-maas/7297
Edit2:
Same error with a custom centos8-stream image.
The custom image was built with stock configuration from the template.
So the solution must be within MAAS or the import command.
I used the same command as mentioned above.
Edit3:
| Fri, 11 Aug. 2023 10:20:43 | HTTP Request - /images/custom/amd64/ga-20.04/cenost8stream/no-such-image/boot-kernel |
|---|---|
| Fri, 11 Aug. 2023 10:20:43 | Marking node failed - Missing boot image custom/amd64/ga-20.04/cenost8stream. |
| Fri, 11 Aug. 2023 10:20:43 | HTTP Request - pxelinux.cfg/01-00-50-56-8b-25-d9 |
| Fri, 11 Aug. 2023 10:20:43 | Performing PXE boot |