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 [wily-server-cloudimg-armhf.img]== === /etc/kernel-img.conf === # Kernel Image management overrides # See kernel-img.conf(5) for details do_symlinks = Yes === /etc/cloud/build.info === build_name: server serial: 20160123 == wily arm64 [wily-server-cloudimg-arm64.img]== === /etc/kernel-img.conf === # Kernel Image management overrides # See kernel-img.conf(5) for details do_symlinks = Yes === /etc/cloud/build.info === build_name: server serial: 20160123 == wily amd64 [wily-server-cloudimg-amd64.img]== === /etc/kernel-img.conf === # Kernel Image management overrides # See kernel-img.conf(5) for details do_symlinks = Yes === /etc/cloud/build.info === build_name: server serial: 20160123 == wily ppc64el [wily-server-cloudimg-ppc64el.img]== === /etc/kernel-img.conf === # Kernel Image management overrides # See kernel-img.conf(5) for details do_symlinks = Yes === /etc/cloud/build.info === build_name: server serial: 20160123 == xenial armhf [xenial-server-cloudimg-armhf.img]== === /etc/kernel-img.conf === # Kernel Image management overrides # See kernel-img.conf(5) for details do_symlinks = yes do_bootloader = no link_in_boot = yes === /etc/cloud/build.info === build_name: server serial: 20160125-134444 == xenial arm64 [xenial-server-cloudimg-arm64.img]== === /etc/kernel-img.conf === # Kernel Image management overrides # See kernel-img.conf(5) for details do_symlinks = yes do_bootloader = no link_in_boot = yes === /etc/cloud/build.info === build_name: server serial: 20160125-134444 == xenial amd64 [xenial-server-cloudimg-amd64.img]== === /etc/kernel-img.conf === # Kernel Image management overrides # See kernel-img.conf(5) for details do_symlinks = yes do_bootloader = no === /etc/cloud/build.info === build_name: server serial: 20160125-134444 == xenial ppc64el [xenial-server-cloudimg-ppc64el.img]== === /etc/kernel-img.conf === # Kernel Image management overrides # See kernel-img.conf(5) for details do_symlinks = yes do_bootloader = no link_in_boot = yes === /etc/cloud/build.info === build_name: server serial: 20160125-134444 ** Attachment added: "show-kernel-img-conf" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1536810/+attachment/4556474/+files/show-kernel-img-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 ‘/boot/initrd.img-4.3.0-7-generic’: No such file or directory Status in linux package in Ubuntu: Confirmed Bug description: 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 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 directory Failed to copy /boot/initrd.img-4.3.0-7-generic to /boot/initrd.img at /var/lib/dpkg/info/linux-image-4.3.0-7-generic.postinst line 745. dpkg: error processing package linux-image-4.3.0-7-generic (--configure): subprocess installed post-installation script returned error exit status 2 Setting up devio (1.2-1build2) ... Setting up linux-base (4.0ubuntu1) ... Setting up flash-kernel (3.0~rc.4ubuntu57) ... Setting up linux-firmware (1.155) ... dpkg: dependency problems prevent configuration of linux-image-generic: linux-image-generic depends on linux-image-4.3.0-7-generic; however: Package linux-image-4.3.0-7-generic is not configured yet. dpkg: error processing package linux-image-generic (--configure): dependency problems - leaving unconfigured Setting up linux-headers-4.3.0-7 (4.3.0-7.18) ... Setting up linux-headers-4.3.0-7-generic (4.3.0-7.18) ... Setting up linux-headers-generic (4.3.0.7.8) ... dpkg: dependency problems prevent configuration of linux-generic: linux-generic depends on linux-image-generic (= 4.3.0.7.8); however: Package linux-image-generic is not configured yet. dpkg: error processing package linux-generic (--configure): dependency problems - leaving unconfigured No apport report written because the error message indicates its a followup error from a previous failure. No apport report written because the error message indicates its a followup error from a previous failure. Errors were encountered while processing: linux-image-4.3.0-7-generic linux-image-generic linux-generic E: Sub-process /usr/bin/dpkg returned an error code (1) failed install of linux-generic failed chroot and kernel install failed failed to get linux-generic output To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1536810/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
