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

[Scott Moser]

** Description changed:

  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

-- 
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:
  New

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

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