[Bug 1517586] Please test proposed package

[Chris J Arges]

Hello Mathieu, or anyone else affected,

Accepted grub2-signed into trusty-proposed. The package will build now
and be available at
https://launchpad.net/ubuntu/+source/grub2-signed/1.34.6 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 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 to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

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

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

Title:
  can't boot to disk from netboot on power8

Status in grub2 package in Ubuntu:
  Fix Released
Status in grub2 source package in Trusty:
  Fix Committed
Status in grub2 source package in Vivid:
  Fix Committed
Status in grub2 source package in Wily:
  Fix Committed

Bug description:
  [Impact]
  This affects users of POWER systems booting from the network in an attempt to boot the system on disk via grub2, as is typically done in MAAS-based installs and system provisioning.

  [Test case]
  - Attempt to boot the system from the network to grub; in order to boot off the local disk.
  -or-
  - Attempt to fully provision a system using MAAS, from starting the installer to rebooting to the installed system using the MAAS features to Deploy and Acquire a system.

  [Regression Potential]
  This modification introduces new work to be done by grub to spin up and detect disks from the ofdisk module; in turn, this may increase delay in booting to the point of reaching a timeout (failure to boot). Possible regressions might include booting to an incorrect device due to more devices being available for grub to peruse, which could mean changes to the device numbering due to more devices being detected (systems failing to boot following the update due to device numbering changes, rendering working grub.cfg configs ineffective).

  --

  It should be possible to use BOOTP to boot from the network, and then
  tell a PowerVM node to local boot via grub2.

  Unfortunately, this fails as it cannot see the disks/partitions.

  Upstream has a fix committed to solve the problem:
  http://git.savannah.gnu.org/cgit/grub.git/commit/?id=c899d9f42c543939abc92d79c9729d429740492e

  This patch should be cherry-picked.

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