[Bug 1913437] [NEW] apt-get installs grub-pc package 2.02-2ubuntu8.21 without errors, but the machine fails to boot

[Rudolf Visagie]

Public bug reported:

We are creating AWS AMIs using an EBS surrogate and running this command
which completes successfully without any errors (only specific package
shown):

Distribution: bionic

apt-get install -y --no-install-recommends grub-pc

Afterwards when we check the /grub directory it is incomplete:

ls -l grub/
total 2348
-rw-r--r-- 1 root root 712 Jan 26 08:18 gfxblacklist.txt
-rw-r--r-- 1 root root 2397557 Jan 26 08:18 unicode.pf2

An instance created using the AMI also fails to boot with the following
error:

No bootable disk

The grub-pc version installed is 2.02-2ubuntu8.21.

If we install grub manually using grub-install and grub-mkconfig it
works with the same version (2.02-2ubuntu8.21).

The above mentioned automated AMI creation process running apt-get also
works if we downgrade to version 2.02-2ubuntu8.17.

Previously we created images with version 2.02-2ubuntu8.18 (as that was
the current version at the time) and it worked perfectly, but we noticed
that this has been removed from the Ubuntu archive:
http://archive.ubuntu.com/ubuntu/pool/main/g/grub2/ (only
2.02-2ubuntu8.17 and 2.02-2ubuntu8.21 still available).

>From the changelog it seems likely that the breaking change could have
been introduced here:
https://launchpad.net/ubuntu/+source/grub2/2.02-2ubuntu8.19

** Affects: grub2 (Ubuntu)
     Importance: Undecided
         Status: New

** Description changed:

  We are creating AWS AMIs using an EBS surrogate and running this command
  (only specific package shown):
  
  Distribution: bionic
  
  apt-get install -y --no-install-recommends grub-pc
  
- Afterwards when we check the /grub folder it is incomplete:
+ Afterwards when we check the /grub directory it is incomplete:
  
  ls -l grub/
  total 2348
  -rw-r--r-- 1 root root 712 Jan 26 08:18 gfxblacklist.txt
  -rw-r--r-- 1 root root 2397557 Jan 26 08:18 unicode.pf2
  
  An instance created using the AMI also fails to boot with the following
  error:
  
  No bootable disk
  
  The grub-pc version installed is 2.02-2ubuntu8.21.
  
  If we install grub manually using grub-install and grub-mkconfig it
  works with the same version (2.02-2ubuntu8.21).
  
  The above mentioned automated AMI creation process running apt-get also
  works if we downgrade to version 2.02-2ubuntu8.17.
  
  Previously we created images with version 2.02-2ubuntu8.18 (as that was
  the current version at the time) and it worked perfectly, but we noticed
  that this has been removed from the Ubuntu archive:
  http://archive.ubuntu.com/ubuntu/pool/main/g/grub2/ (only
  2.02-2ubuntu8.17 and 2.02-2ubuntu8.21 still available).
  
  From the changelog it seems likely that the breaking change could have
  been introduced here:
  https://launchpad.net/ubuntu/+source/grub2/2.02-2ubuntu8.19

** Description changed:

  We are creating AWS AMIs using an EBS surrogate and running this command
- (only specific package shown):
+ which completes successfully without any errors (only specific package
+ shown):
  
  Distribution: bionic
  
  apt-get install -y --no-install-recommends grub-pc
  
  Afterwards when we check the /grub directory it is incomplete:
  
  ls -l grub/
  total 2348
  -rw-r--r-- 1 root root 712 Jan 26 08:18 gfxblacklist.txt
  -rw-r--r-- 1 root root 2397557 Jan 26 08:18 unicode.pf2
  
  An instance created using the AMI also fails to boot with the following
  error:
  
  No bootable disk
  
  The grub-pc version installed is 2.02-2ubuntu8.21.
  
  If we install grub manually using grub-install and grub-mkconfig it
  works with the same version (2.02-2ubuntu8.21).
  
  The above mentioned automated AMI creation process running apt-get also
  works if we downgrade to version 2.02-2ubuntu8.17.
  
  Previously we created images with version 2.02-2ubuntu8.18 (as that was
  the current version at the time) and it worked perfectly, but we noticed
  that this has been removed from the Ubuntu archive:
  http://archive.ubuntu.com/ubuntu/pool/main/g/grub2/ (only
  2.02-2ubuntu8.17 and 2.02-2ubuntu8.21 still available).
  
  From the changelog it seems likely that the breaking change could have
  been introduced here:
  https://launchpad.net/ubuntu/+source/grub2/2.02-2ubuntu8.19

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

Title:
  apt-get  installs grub-pc package 2.02-2ubuntu8.21 without errors, but
  the machine fails to boot

Status in grub2 package in Ubuntu:
  New

Bug description:
  We are creating AWS AMIs using an EBS surrogate and running this
  command which completes successfully without any errors (only specific
  package shown):

  Distribution: bionic

  apt-get install -y --no-install-recommends grub-pc

  Afterwards when we check the /grub directory it is incomplete:

  ls -l grub/
  total 2348
  -rw-r--r-- 1 root root 712 Jan 26 08:18 gfxblacklist.txt
  -rw-r--r-- 1 root root 2397557 Jan 26 08:18 unicode.pf2

  An instance created using the AMI also fails to boot with the
  following error:

  No bootable disk

  The grub-pc version installed is 2.02-2ubuntu8.21.

  If we install grub manually using grub-install and grub-mkconfig it
  works with the same version (2.02-2ubuntu8.21).

  The above mentioned automated AMI creation process running apt-get
  also works if we downgrade to version 2.02-2ubuntu8.17.

  Previously we created images with version 2.02-2ubuntu8.18 (as that
  was the current version at the time) and it worked perfectly, but we
  noticed that this has been removed from the Ubuntu archive:
  http://archive.ubuntu.com/ubuntu/pool/main/g/grub2/ (only
  2.02-2ubuntu8.17 and 2.02-2ubuntu8.21 still available).

  From the changelog it seems likely that the breaking change could have
  been introduced here:
  https://launchpad.net/ubuntu/+source/grub2/2.02-2ubuntu8.19

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