Even when a node has been deployed, the node still attempts to PXE boot from MAAS each time it's rebooted. MAAS knows it should boot locally and gives the following configuration to PXELINUX:
DEFAULT local LABEL local LOCALBOOT 0 It appears that this does not do the right thing for your hardware. Put another way, it does not do the same thing as your machine's BIOS does when the network is unavailable. I suspect this is a bug in PXELINUX and/or your hardare. There may be something that MAAS can do to help, but I don't think it's the cause, so I'll target this bug at PXELINUX and mark it Invalid in MAAS for now. ** Also affects: syslinux (Ubuntu) Importance: Undecided Status: New ** Changed in: maas Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1488594 Title: Nodes cannot boot after a storage disk replacement To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1488594/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs