[Bug 1812863] Re: No way to debug grub.cfg generation

[Launchpad Bug Tracker]

This bug was fixed in the package grub2 - 2.02-2ubuntu8.10

---------------
grub2 (2.02-2ubuntu8.10) bionic; urgency=medium

  [ Mathieu Trudel-Lapierre ]
  * debian/grub-check-signatures: check kernel signatures against keys known
    in firmware, in case a kernel is signed but not using a key that will pass
    validation, such as when using kernels coming from a PPA. (LP: #1789918)
  * debian/patches/mkconfig_leave_breadcrumbs.patch: make sure grub-mkconfig
    leaves a trace of what files were sourced to help generate the config
    we're building. (LP: #1812863)

  [ Steve Langasek ]
  * debian/patches/quick-boot-lvm.patch: If we don't have writable
    grubenv and we're on EFI, always show the menu.  Closes LP: #1800722.

 -- Mathieu Trudel-Lapierre <cyphermox at ubuntu.com>  Wed, 09 Jan 2019
14:04:09 -0500

** Changed in: grub2 (Ubuntu Bionic)
       Status: Fix Committed => Fix Released

-- 
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/1812863

Title:
  No way to debug grub.cfg generation

Status in grub2 package in Ubuntu:
  Fix Released
Status in grub2 source package in Bionic:
  Fix Released
Status in grub2 source package in Cosmic:
  Fix Released

Bug description:
  [Impact]
  Any user who wants to understand how /boot/grub/grub.cfg is being generated. This is especially useful on dynamically-deployed systems (ie. using MAAS, cloud-init) on clouds or datacenter deployments.

  [Test case]
  1) Run 'update-grub'
  2) Verify that messages are displayed to describe which files are being read:

  $ sudo update-grub 
  Sourcing file `/etc/default/grub'
  Generating grub configuration file ...
  [...]

  
  [Regression potential]
  Watch out for any issues generating a correct and/or complete grub.cfg for next boot; missing kernels in the boot menu, or any missing kernel command-line parameters for a kernel booted after grub.cfg has been regenerated.

  ---

  It's really hard to debug what happens to generate grub.cfg -- no way
  to know what files (from /etc/default/grub, /etc/default/grub.d/*) are
  being used in which order.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1812863/+subscriptions