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 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 [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
