[Bug 1743249] Re: Failed Deployment after timeout trying to retrieve grub cfg

[Steve Langasek]

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
Foundations Bugs, which is subscribed to grub2 in Ubuntu.
https://bugs.launchpad.net/bugs/1743249

Title:
  Failed Deployment after timeout trying to retrieve grub cfg

Status in MAAS:
  New
Status in grub2 package in Ubuntu:
  In Progress

Bug description:
  A node failed to deploy after it failed to retrieve a grub.cfg from
  MAAS due to a timeout.  In the logs, it's clear that the server tried
  to retrieve the grub cfg many times, over about 30 seconds:

  http://paste.ubuntu.com/26387256/

  We see the same thing for other hosts around the same time:

  http://paste.ubuntu.com/26387262/

  It seems like MAAS is taking way too long to respond to these
  requests.

  This is very similar to bug 1724677, which was happening pre-
  metldown/spectre. The only difference is we don't see "[critical] TFTP
  back-end failed" in the logs anymore.

  I connected to the console on this system and it had errors about
  timing out retrieving the grub-cfg, then it had an error message along
  the lines of "error not an ip" and then "double free".  After I
  connected but before I could get a screenshot the system rebooted and
  was directed by maas to power off, which it did successfully after
  booting to linux.

  Full logs are available here:
  https://10.245.162.101/artifacts/14a34b5a-9321-4d1a-b2fa-
  ed277a020e7c/cpe_cloud_395/infra-logs.tar

  This is with 2.3.0-6434-gd354690-0ubuntu1~16.04.1.

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1743249/+subscriptions