[Bug 1549064] Re: grub-ieee1275 should not change boot-device for every upgrade

[Launchpad Bug Tracker]

This bug was fixed in the package grub2 - 2.02~beta2-9ubuntu1.8

---------------
grub2 (2.02~beta2-9ubuntu1.8) trusty; urgency=medium

  * debian/prep-bootdev.c: add prep-bootdev for use in postinst (and to help
    detecting the prep partition on ppc64el in general).
  * debian/rules: build the prep-bootdev binary for grub-ieee1275.
  * debian/control: add libparted-dev to Build-Depends for prep-bootdev.
  * debian/grub-ieee1275-bin.install.ppc64el.in: ship prep-bootdev.
  * debian/clean: clean up prep-bootdev.
  * debian/postinst.in: (LP: #1549064)
    - run prep-bootdev to have a device to point grub-ieee1275 to to install
      the new bootloader data to when calling grub-install.
    - run grub-install with --no-nvram to avoid clobbering the boot-device
      variable every time grub is updated.

 -- Mathieu Trudel-Lapierre <mathieu-tl at ubuntu.com>  Wed, 24 Feb 2016
14:39:34 -0500

** Changed in: grub2 (Ubuntu Trusty)
       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/1549064

Title:
  grub-ieee1275 should not change boot-device for every upgrade

Status in grub2 package in Ubuntu:
  In Progress
Status in grub2-signed package in Ubuntu:
  Invalid
Status in grub2 source package in Trusty:
  Fix Released
Status in grub2-signed source package in Trusty:
  Fix Released

Bug description:
  [Impact]
  This affects all ppc64el users whenever they upgrade grub.

  [Test case]
  1) run 'nvram --print-config=boot-device'
  2) upgrade grub-ieee1275
  2) run 'nvram --print-config=boot-device'

  The value should not change between runs, it should also not be touched at all (even if it's set to the same value).
  This can be further verified by modifying boot-device to an arbitrary value before running the grub upgrade.

  [Regression potential]
  This has minimal potential for regression. It removes a code path which might otherwise break booting after upgrading grub on the affected systems. One possibility for regression is that if code paths are subsequently added to register openfirmware devices, this should be guarded with an 'if (update_nvram)' test to make sure it only ever happens when the --no-nvram flag is *NOT* passed to grub-install.

  ---

  grub-ieee1275 should call grub-install with --no-nvram in postinst, so
  as not to modify boot-device in OpenFirmware everytime the grub
  package is updated.

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