[Bug 2052382] Re: [os-prober] microcode still in grub.cfg after first update-grub

[Heitor Alves de Siqueira]

Hi all,

I haven't been able to reproduce this following the steps reported in
the bug so far. I've tried simple LXD VMs as well as an AWS instance,
but both seem to be working as expected.

Are you still able to reproduce this? If so, can you post more details
for me to track this down?

** Changed in: os-prober (Ubuntu)
       Status: Confirmed => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to os-prober in Ubuntu.
https://bugs.launchpad.net/bugs/2052382

Title:
  [os-prober] microcode still in grub.cfg after first update-grub

Status in os-prober package in Ubuntu:
  Incomplete

Bug description:
  If you install microcode-initrd and then remove it, after the FIRST
  update-grub, reference to microcode.cpio. but /boot/microcode.cpio
  don't exists anymore, causing boot failure.

  This problem only occure when using os-prober AND having SUBMENU
  enabled in grub.

  This is due to use of /usr/lib/linux-boot-probes/mounted/40grub2, in
  os-prober, wich use grub.cfg, but when update-grub run, it's
  grub.cfg.new which is the new reference.

  I propose managing grub.cfg.new in 40grub2 :

  <code>
  96c96,101
  < if [ -e "$mpoint/boot/grub/grub.cfg" ] && \
  ---
  > # If fresh grub.cfg.new exists, we where in update-grub/grub-mkconfig generation cycle
  > GRUB_NEW=$(find ${mpoint}/boot/grub/ -maxdepth 1 -type f -name grub.cfg.new -mmin -5 || true)
  > if [ -n "${GRUB_NEW}" ];then
  > 	debug "parsing grub.cfg.new"
  >         parse_grub_menu "$mpoint" "$partition" "$bootpart" < "$mpoint/boot/grub/grub.cfg.new"
  > elif [ -e "$mpoint/boot/grub/grub.cfg" ] && \
  <code>

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/os-prober/+bug/2052382/+subscriptions