[Bug 1356569] Re: flash-kernel should not consider ignored kernels as latest

[Narinder Gupta]

** Also affects: lomond
   Importance: Undecided
       Status: New

** Changed in: lomond
     Assignee: (unassigned) => Manoj Iyer (manjo)

** Changed in: lomond
   Importance: Undecided => High

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

Title:
  flash-kernel should not consider ignored kernels as latest

Status in The Lomond project:
  New
Status in “flash-kernel” package in Ubuntu:
  Confirmed
Status in “flash-kernel” source package in Trusty:
  Confirmed
Status in “flash-kernel” source package in Utopic:
  Confirmed

Bug description:
  flash-kernel has logic that tries to determine "is this kernel the latest", so that it will only flash the latest kernel.
  It also has logic that white-lists certain kernel flavors.

  However, when it determines "is this the latest kernel", it does not apply the whitelist.
  This causes issues if you have other kernels installed that are "newer" but would be ignored.

  See the maas/curtin install log at http://paste.ubuntu.com/7955339/

  Specifically, it says:
  | Examining /etc/kernel/postinst.d.
  | run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 3.13.0-8-keystone /boot/vmlinuz-3.13.0-8-keystone
  | run-parts: executing /etc/kernel/postinst.d/initramfs-tools 3.13.0-8-keystone /boot/vmlinuz-3.13.0-8-keystone
  | update-initramfs: Generating /boot/initrd.img-3.13.0-8-keystone
  | df: Warning: cannot read table of mounted file systems: No such file or directory
  | run-parts: executing /etc/kernel/postinst.d/update-notifier 3.13.0-8-keystone /boot/vmlinuz-3.13.0-8-keystone
  | run-parts: executing /etc/kernel/postinst.d/x-grub-legacy-ec2 3.13.0-8-keystone /boot/vmlinuz-3.13.0-8-keystone
  | Searching for GRUB installation directory ... found: /boot/grub
  | Searching for default file ... found: /boot/grub/default
  | Testing for an existing GRUB menu.lst file ... found: /boot/grub/menu.lst
  | Searching for splash image ... none found, skipping ...
  | Ignoring non-Xen Kernel on Xen domU host: vmlinuz-3.13.0-8-keystone
  | Found kernel: /boot/vmlinuz-3.13.0-32-generic
  | Updating /boot/grub/menu.lst ... done
  | 
  | run-parts: executing /etc/kernel/postinst.d/zz-flash-kernel 3.13.0-8-keystone /boot/vmlinuz-3.13.0-8-keystone
  | Ignoring old or unknown version 3.13.0-8-keystone (latest is 3.13.0-32-generic)
  | Setting up linux-headers-3.13.0-8-keystone (3.13.0-8.12) ...
  | Setting up linux-headers-keystone (3.13.0.8.7) ...
  | Setting up linux-image-keystone (3.13.0.8.7) ...
  | Setting up linux-keystone (3.13.0.8.7) ...
  | Leaving 'diversion of /etc/init/ureadahead.conf to /etc/init/ureadahead.conf.disabled by cloud-init'
  | update-initramfs: Generating /boot/initrd.img-3.13.0-32-generic
  | df: Warning: cannot read table of mounted file systems: No such file or directory
  | Kernel suffix generic does not match any of the expected flavors (keystone), therefore not writing it to flash.

  
  Note that it decides not to flash -generic kernel because it is not in the whitelist, but does ignores keystone kernel because it is not the newest.  Result is that nothing is installed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/lomond/+bug/1356569/+subscriptions