This looks like MAAS is not installing a kernel to the machine for deployment, or rescue mode.
Commissioning works great, I am able to monitor the machine’s console, and all is well.
During deployment it seems to work at first, even allowing me to ssh into the system while the deployment is running. However on the final boot, the machine boots up to a “boot:” prompt, which generally tells me that the machine can’t find the kernel.
When I try the rescue mode, it does the same thing.
I’ve been using MAAS for two years with great success, this problem just started yesterday, last week I deployed 8 systems flawlessly as is normal, today I can commission, but not deploy or rescue.
This is true regardless of the version of ubuntu/centos I try to install.
Interestingly when I run rescue mode I get a message:
Loading ubuntu/amd64/ga-1804/xenial/no-such-image/boot-kernel… failed: No such file or directory
This may be a side effect of another problem that I had about a month ago. During a image sync, one of the images got stuck at 12% because my ISP had an outage. Nothing I would do could get the sync to restart. However deployments were still working, they didn’t start failing until yesterday (4/23). After deployments started failing, I decided to try and fix the stuck sync. Telling MAAS to stop syncing that image did not work, but after an update which brought maas up to 2.4.2, I was able to deslect all of my images, and re-select them to fetch fresh ones. However that did not fix my deploy problem.
We mainly deploy centos7 as our application is certified for RHEL, but when centos fails I can generally get ubuntu to work… But not it seems like nothing works, every deployment or rescue results in a system that boots up to the point it can’t find the kernel. But the kernel used for commissioning and deployment does work, so the problem seems to be in the part of the deployment scripts where the kernel is installed, and seems to impact everything.
There is nothing custom in my MAAS, other than simple configuration.