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

[Mathieu Trudel-Lapierre]

** Description changed:

+ [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.

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

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