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

Jason Hobbs jason.hobbs at canonical.com
Thu Feb 1 16:26:47 UTC 2018


In the pcap from comment #35, MAAS eventually does respond to the
interface specific grub request, 61 seconds after the request, after
it's already sent the grub.cfg-default-amd64, kernel, and initrd. You
can see the responses to the interface specific grub.cfg requests coming
back starting at packet 90573.

While Steve's finding in #33/34 seem to indicate a grub bug, this seems
like a MAAS problem occurring before that grub bug even has a chance to
take effect.  I'm attaching MAAS logs from this same test run.

>From the maas logs, the requests start at 01:02:49
logs-2018-02-01-01.04.49/10.244.40.30/var/log/maas/rackd.log

There are some "critical" tftp errors logged in the same file not long afterwards:
http://paste.ubuntu.com/26501394/

There are errors in postgresl's log around the same time too:
(logs-2018-02-01-01.04.49/10.244.40.30/var/log/postgresql$ vim postgresql-9.5-ha.log)

http://paste.ubuntu.com/26501399/

** Attachment added: "infra-logs.tar"
   https://bugs.launchpad.net/maas/+bug/1743249/+attachment/5046970/+files/infra-logs.tar

-- 
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:
  Incomplete
Status in grub2 package in Ubuntu:
  New

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



More information about the foundations-bugs mailing list