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

[Brian Murray]

Hello Mathieu, or anyone else affected,

Accepted grub2 into cosmic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/grub2/2.02+dfsg1-5ubuntu8.1 in a
few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-cosmic to verification-done-cosmic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-cosmic. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: grub2 (Ubuntu Cosmic)
       Status: New => Fix Committed

** Tags added: verification-needed verification-needed-cosmic

-- 
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 Committed
Status in grub2 source package in Cosmic:
  Fix Committed

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