** Also affects: live-build (Ubuntu Xenial)
Importance: Undecided
Status: New
** 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
+
+ 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.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to 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
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/live-build/+bug/1539157/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
