[Bug 1517586] Re: can't boot to disk from netboot on power8

[Launchpad Bug Tracker]

This bug was fixed in the package grub2-signed - 1.46.5

---------------
grub2-signed (1.46.5) vivid; urgency=medium

  * Rebuild against grub2 2.02~beta2-22ubuntu1.5 (LP: #1476882, LP: #1459872,
    LP: 1459871, LP: #1517586, LP:#1508893, LP: #1521612, LP: #1274320).

 -- dann frazier <dannf at ubuntu.com>  Wed, 16 Dec 2015 14:18:28 -0700

** Changed in: grub2 (Ubuntu Wily)
       Status: Fix Committed => Fix Released

-- 
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-signed package in Ubuntu:
  Fix Released
Status in grub2 source package in Trusty:
  Fix Released
Status in grub2-signed source package in Trusty:
  Fix Released
Status in grub2 source package in Vivid:
  Fix Released
Status in grub2-signed source package in Vivid:
  Fix Released
Status in grub2 source package in Wily:
  Fix Released
Status in grub2-signed source package in Wily:
  Fix Released

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