Comment 38 for bug 1532935

Cool!

Now the question is where in grub-install from grub-efi package does it
write out that file and why would it not include that last line; seems
boilerplate to me.

You might want to target this bug against the grub package.

On Fri, May 20, 2016 at 5:26 PM, John George <email address hidden>
wrote:

> Both servers, that are stopping at the grub menu, indeed do not have the
> 'configfile $prefix/grub.cfg' line in their
> /boot/efi/EFI/ubuntu/grub.cfg file.
>
> Adding that line allows them to boot without stopping at the grub
> prompt.
>
> I released both of these server and re-deployed Trusty from the MAAS.
> Again they stopped at grub and did not have the configfile line in
> grub.cfg. Manually triggering the server to come up with:
>
> grub> linux /boot/vmlinuz-3.13.0-86-generic root=LABEL=root ro
> console=ttyS1,38400
> grub> initrd /boot/initrd.img-3.13.0-86-generic
> grub> boot
>
> Once the system was up, the MAAS state changed to deployed. Any re-boots
> would stop of the grub menu until I manually add the 'configfile
> $prefix/grub.cfg' line to the /boot/efi/EFI/ubuntu/grub.cfg file.
>
> Ryan you appear to have identified the issue here.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1532935
>
> Title:
> Nodes stuck at grub menu when attempting to deploy
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/curtin/+bug/1532935/+subscriptions
>