On Mon, Feb 05, 2018 at 08:40:56PM -0000, Jason Hobbs wrote: > @Steve - I don't think it helps with the problem of MAAS taking a long > time to respond to the grub.cfg request. However, it may help with the > part of this bug where grub is hitting an error and asking for keyboard > input. https://imgur.com/a/as8Sx
> Maybe that should be a separate bug? It seems like grub should never > ask for user keyboard input on a server. Perhaps that bug is fixed as a side effect of the grub change. But 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? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1743249 Title: Failed Deployment after timeout trying to retrieve grub cfg To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1743249/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
