We are seeing another variant of this, where nodes end up powered off instead of hung. What happens there is:
1) Node tries to get grub.cfg-<mac> over and over until it gives up.
2) Node tries to get grub.cfg-default-amd64, and succeeds.
3) This results in the node getting directed to enlist as a new node, since MAAS doesn't have anything to recognize it by at this point.
4) After running the enlistment scripts, the node powers off.
We are seeing this variant even with kpti disabled.
We are seeing another variant of this, where nodes end up powered off instead of hung. What happens there is:
1) Node tries to get grub.cfg-<mac> over and over until it gives up. default- amd64, and succeeds.
2) Node tries to get grub.cfg-
3) This results in the node getting directed to enlist as a new node, since MAAS doesn't have anything to recognize it by at this point.
4) After running the enlistment scripts, the node powers off.
We are seeing this variant even with kpti disabled.