group.of.nepali.translators team mailing list archive

[Launchpad Bug Tracker <1655934@xxxxxxxxxxxxxxxxxx>]

This bug was fixed in the package cloud-init - 0.7.9-0ubuntu2

---------------
cloud-init (0.7.9-0ubuntu2) zesty; urgency=medium

  * debian/update-grub-legacy-ec2:
    - Correctly detect kernels ending in -aws as kernels that can boot on EC2
      (LP: #1655934)

 -- Daniel Watkins <daniel.watkins@xxxxxxxxxxxxx>  Thu, 12 Jan 2017
11:34:23 +0000

** Changed in: cloud-init (Ubuntu)
       Status: New => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1655934

Title:
  update-grub-legacy-ec2 should detect -aws kernels as appropriate for
  EC2

Status in cloud-init package in Ubuntu:
  Fix Committed
Status in cloud-init source package in Xenial:
  New

Bug description:
  [Impact]
  PV images built with AWS custom kernels currently won't boot because their kernels aren't detected.

  [Test Case]

  * Launch an HVM instance
  * Run update-grub-legacy-ec2 and see an error message like "Ignoring non-Xen Kernel on Xen domU host: vmlinuz-4.4.0-1001-aws"
  * Install the new package
  * Run update-grub-legacy-ec2 again and see success like:
  Found kernel: /boot/vmlinuz-4.4.0-1001-aws
  Found kernel: /boot/vmlinuz-4.4.0-1001-aws
  Updating /boot/grub/menu.lst ... done

  [Regression Potential]
  This is a single line change to a case statement; regression potential is minimal.

  [Original Report]
  Currently, it will detect -ec2 kernels, but we also need it to detect -aws kernels.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1655934/+subscriptions