Steve, Sorry, I missed comment #65 on the original bug.
I think this is a bit different question than what to do when it can't find the file. In that bug, grub has been instructed to fall back to grub.cfg-default-amd64 if it can't find the file. In some cases it does, but in others it displays the error message linked above and hangs up. I don't know what happens if it tries to get grub.cfg-default-amd64 and can't - we haven't ever run into that. In the case of not being able to find the file, or of an error, I think it should go back to UEFI and let UEFI handle it as a failed boot/can't boot from that device, and let UEFI handle that however it handles it. I think that's better because it leaves it up to UEFI to handle it just like it would any other failed boot. If that's by rebooting, or retrying the boot devices, things may work the second time, for example, if the network boot server is no longer overloaded. Looking at the grub code, it only halts in grub_abort() if grub thinks there is an input method available. I guess there technically is one available here because you could login via remote console on the BMC and input text.. but that doesn't seem very friendly. Jason On Wed, Feb 7, 2018 at 11:30 AM, Steve Langasek <steve.langa...@canonical.com> wrote: > As I asked in https://bugs.launchpad.net/maas/+bug/1743249/comments/65: > > What do you think the correct behavior should be when grub cannot find > the file that it needs in order to boot? Should grub enter a boot loop, > retrying endlessly? Should it try to halt the system? Why is either of > these options more correct than putting the machine to a console prompt? > > ** Changed in: grub2 (Ubuntu) > Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1747927 > > Title: > when net booting servers with MAAS, grub should never wait for user > input to reboot > > Status in grub2 package in Ubuntu: > Incomplete > > Bug description: > In bug 1743249, grub sometimes would hang waiting for user input on > the keyboard. This is never an appropriate action for a net booting > server, at least not one booting under MAAS direction. It may be > appropriate to pause for 30 seconds or something so someone can see > the error, but to just hang is wrong. > > > https://imgur.com/a/as8Sx > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1747927/+subscriptions ** Tags removed: cdo-qa-blocker ** Changed in: grub2 (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1747927 Title: when net booting servers with MAAS, grub should never wait for user input to reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1747927/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
