The CentOS image was downloaded using the WebUI options and can be deployed. It's the official one.
If I interrupt the installation, the machine will go into "Failed deployment" state,
and subsequent boots will show the "invalid magic number" and that event is generated before that.
Here is the output of maas $PROFILE boot-resources read:
The CentOS image was downloaded using the WebUI options and can be deployed. It's the official one.
If I interrupt the installation, the machine will go into "Failed deployment" state,
and subsequent boots will show the "invalid magic number" and that event is generated before that.
Here is the output of maas $PROFILE boot-resources read:
https:/ /paste. ubuntu. com/p/z6jY9kBgZ R/
I believe that message is generated by the tftp daemon here:
https:/ /github. com/maas/ maas/blob/ master/ src/provisionin gserver/ rackdservices/ tftp.py# L211
Because centos and custom images don't have a commissioning image, only an xinstall one,
and purpose on the next boot is set to commissioning.
https:/ /github. com/maas/ maas/blob/ master/ src/provisionin gserver/ rackdservices/ tftp.py# L289
This problem was reported in MAAS 3.2.9/debs and my reproducer is using MAAS 3.3.4/debs.
I just launched a new instance with MAAS 3.4.0~rc2 using snaps and I can reproduce the issue.