Verified fixed in arm64 image for 20160227.
I noticed it does still have the bogus 'initrd.img file:
$ ls -l $exdir/boot
total 20592
drwxr-xr-x 2 root root 4096 Feb 27 14:36 grub
-rw-r--r-- 1 root root 21079648 Feb 27 14:38 initrd.img
But the initrd.img file does not seem to cause a problem
This bug was fixed in the package linux - 4.4.0-8.23
---
linux (4.4.0-8.23) xenial; urgency=low
* cgroup namespace mounts broken in containers (LP: #1549398)
- SAUCE: kernfs: Always set super block owner to init_user_ns
* 4.4.0-7.22 no longer boots on arm64 (LP: #1547718)
Reproduce for this issue is as simple as downloading -root.tar.xz (or
-root.tar.gz) from http://cloud-images.ubuntu.com/daily/server/xenial ,
then extracting it, chrooting and apt-get installing a kernel.
I believe that amd64 works fine, so to see failure you have to either
use qemu-user-static
** Changed in: linux (Ubuntu)
Status: Confirmed => In Progress
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Andy Whitcroft (apw)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
This really never got fixed to my knowledge.
https://pastebin.canonical.com/150018/ shows the general failure occuring on
arm64.
** Changed in: linux (Ubuntu)
Status: Fix Released => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is
This bug was fixed in the package linux - 4.4.0-4.19
---
linux (4.4.0-4.19) xenial; urgency=low
* update ZFS and SPL to 0.6.5.4 (LP: #1542296)
- [Config] update spl/zfs version
- SAUCE: (noup) Update spl to 0.6.5.4-0ubuntu2, zfs to 0.6.5.4-0ubuntu1
- [Config]
I have applied the intent of that fix to our postinst and uploaded an
s390x only kernel to ppa:canonical-kernel-team/ubuntu/unstable. If
someone could test that all the better.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
@xnox says this fixes things for him, so applied to xenial for the next
upload.
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Looking at the postinst script, it calls update-initramfs -u and expects
it to do somethin, i.e. create the initramfs.
However, it can choose to not do so, and deffer the update. And thus not
create an initramfs. However, when we are upgrading to a new kernel
image, we expect to generate an
** Patch added: "linux-postinst.patch"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1536810/+attachment/4560470/+files/linux-postinst.patch
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Tags added: patch
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1536810
Title:
kernel install failed /bin/cp: cannot stat
‘/boot/initrd.img-4.3.0-7-generic’: No such file or
however, as per irc, that will kill the benefit of deffered initramfs
generation.
Identified to cherrypick
https://anonscm.debian.org/cgit/kernel/linux.git/commit/?id=373d086904305699561b1eb505c33b010c24de9b
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=738707
** Bug watch added: Debian
It looks like this file is created by live-build/scripts/build
/lb_chroot_linux-image:
cat > chroot/etc/kernel-img.conf << EOF
# Kernel Image management overrides
# See kernel-img.conf(5) for details
do_symlinks = yes
do_bootloader = no
EOF
case "${LB_ARCHITECTURES}" in
link_in_boot is required as yes for s390x, and currently it seems like
cloud-image generation is broken for s390x.
Manually, upgrading from an older cloudimage (3.3 -6- version) I had to
do a small dpkg remove surgery to drop all the packages, and reinstall
new metapackages.
What I found
** Description changed:
Hi, this failure for kernel package installation occured inside a maas image
(lp:maas-images) build process.
The failure log ends like this:
Unpacking linux-generic (4.3.0.7.8) ...
Processing triggers for man-db (2.7.5-1) ...
Setting up
Hm, i don't think update-initramfs does the right thing:
linux-image-*)
if [ -z "$INITRAMFS_TOOLS_KERNEL_HOOK" ]; then
# kernel maintainer script called us directly; ignore
# it and let the hook script handle it instead
echo
Unpacking linux-generic (4.3.0.7.8) ...
Processing triggers for man-db (2.7.5-1) ...
Setting up linux-image-4.3.0-7-generic (4.3.0-7.18) ...
Running depmod.
update-initramfs: deferring update (hook will be called later)
/bin/cp: cannot stat '/boot/initrd.img-4.3.0-7-generic': No such file or
We really need to understand what is creating this file because
apparently in live build, its not the installation of a kernel.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1536810
@smoser -- the header in your files implies that the kernel at least
created the configuration in the first instance:
print CONF "# Kernel Image management overrides\n";
print CONF "# See kernel-img.conf(5) for details\n";
Though it only appears to write two combinations:
"the kernel at least created the configuration".
I don't know where the file came from, but that is the file that is in
official ubuntu cloud images, built by livefs.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
what provides (or should create) /etc/kernel.conf ?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1536810
Title:
kernel install failed /bin/cp: cannot stat
I've checked, and the file exists. the content is
# Kernel Image management overrides
# See kernel-img.conf(5) for details
do_symlinks = yes
do_bootloader = no
link_in_boot = yes
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
For reference, show-kernel-img-conf.
this downloads cloud images and extracts the questioned file.
Note, there is a change in this file from wily to xenial, but the change is in
place for all arch, and i'm only seeing these build failures in arm64 and armhf.
== wily armhf
** Attachment added: "script reproducing problem"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1536810/+attachment/4556461/+files/reproduce.sh
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Note, there are 2 changes fom wily to xenial in the content of that file:
a.) for arches other than amd64, we gain the 'link_in_boot = yes'
b.) there is a case change for the 'do_symlinks' setting from wily ('Yes') to
xenial ('yes')
--
You received this bug notification because you are a
It seems to be 'a' that causes the failure.
If i remove 'link_in_boot' then it works.
I've committed a change to maas-iamges to work around this at least temporarily
http://bazaar.launchpad.net/~maas-images-maintainers/maas-images/maas-ephemerals/revision/268
--
You received this bug
@smoser -- this occurs when initramfs-tools is unable to use symlinks to
reference the initrd. It then thinks it should copy the newly built one
to /initrd which it cannot do because it is not yet built. This should
never occur because we always use symlinks unless some configuration is
lost,
It'd be nice to track down why images have this change from wily in
them, especially since it is not helpful.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1536810
Title:
kernel
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1536810
Title:
kernel install failed /bin/cp: cannot stat
For full disclosure, this is in a "cross" build environment (qemu-static).
this works for other versions of ubuntu and has worked for xenial in the past.
the error messages seem to indicate 'update-initramfs' was deferred, but
the the postinst tried to copy it into place even though it wasnt
30 matches
Mail list logo
