[Bug 1539157] Re: Images built with "link_in_boot = yes" in /etc/kernel-img.conf end up with a broken /boot/initrd.img

[Andy Whitcroft]

Hello Dan, or anyone else affected,

Accepted live-build into xenial-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/live-
build/3.0~a57-1ubuntu25.1 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!

** Changed in: live-build (Ubuntu Xenial)
       Status: New => Fix Committed

** Tags added: verification-needed

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

Title:
  Images built with "link_in_boot = yes" in /etc/kernel-img.conf end up
  with a broken /boot/initrd.img

Status in live-build package in Ubuntu:
  In Progress
Status in live-build source package in Xenial:
  Fix Committed

Bug description:
  Some architectures get "link_in_boot = yes" added to /etc/kernel-
  img.conf by lb_chroot_linux-image; it appears that cloud images built
  for these architectures (I have checked s390x and arm64) end up with
  an LZMA-compressed empty regular file at /boot/initrd.img (instead of
  the expected symlink to /boot/initrd.img-...).

  In terms of time-of-introduction, I have confirmed that an s390x image
  built against proposed on the 12th of January was good, whereas an
  s390x image built against the main archive on the 25th was not.

  (I suspect that this is actually an issue in something in the archive,
  but as I don't really know _what_, I have filed this against live-
  build for now.)

  Related bugs:
   * bug 1539157: Images built with "link_in_boot = yes" in /etc/kernel-img.conf end up with a broken /boot/initrd.img
   * bug 1536810 kernel install failed /bin/cp: cannot stat ‘/boot/initrd.img-4.3.0-7-generic’: No such file or directory

  For SRU purposes, we can confirm a fix by making sure that cloud
  images of a couple of architectures built with this fix still boot,
  and that initrd.img is a symlink rather than a (small) regular file.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/live-build/+bug/1539157/+subscriptions