[Bug 1541575] Re: zipl-installer: set up re-IPL to boot newly installed Ubuntu/Linux

[Launchpad Bug Tracker]

This bug was fixed in the package zipl-installer - 0.0.32ubuntu1

---------------
zipl-installer (0.0.32ubuntu1) xenial; urgency=low

  * Merge from Debian unstable.  Remaining changes:
    - Apply ubuntu branding.

zipl-installer (0.0.32) unstable; urgency=medium

  [ Hendrik Brueckner ]
  * Mount /sys and /dev before running zipl.
  * Setup re-IPL settings. (Closes: #813506) LP: #1541575

zipl-installer (0.0.31) unstable; urgency=medium

  [ Colin Watson ]
  * Use HTTPS for Vcs-* URLs, and link to cgit rather than gitweb.

 -- Dimitri John Ledkov <xnox at ubuntu.com>  Mon, 29 Feb 2016 08:36:01
+0000

** Changed in: zipl-installer (Ubuntu)
       Status: Fix Committed => Fix Released

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

Title:
  zipl-installer: set up re-IPL to boot newly installed Ubuntu/Linux

Status in zipl-installer package in Ubuntu:
  Fix Released
Status in zipl-installer package in Debian:
  Fix Released

Bug description:
  When an Ubuntu 16.04 system is installed (20101020ubuntu415), the
  system finally shuts down, but does not re-IPL from the target device.

  To set up the re-IPL settings, a call to chreipl is required from
  within the installed system.  This is required beccause chreipl uses a
  helper script to detect the IPL device for linear mapped devices, for
  example, LVM or multipath devices.

  Note that there is also a change required for the rootskel package to
  reset the debian-installer/exit/always_halt to false.

  Please pick up the patches provided in https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=813506 which fix this problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zipl-installer/+bug/1541575/+subscriptions