group.of.nepali.translators team mailing list archive

[Scott Moser <smoser@xxxxxxxxxx>]

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

** Also affects: cloud-init (Ubuntu Zesty)
   Importance: Undecided
     Assignee: Dan Watkins (daniel-thewatkins)
       Status: Fix Committed

** Also affects: cloud-init (Ubuntu Trusty)
   Importance: Undecided
       Status: New

** Also affects: cloud-init (Ubuntu Yakkety)
   Importance: Undecided
       Status: New

** Changed in: cloud-init (Ubuntu Yakkety)
       Status: New => Confirmed

-- 
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 Trusty:
  New
Status in cloud-init source package in Xenial:
  Fix Released
Status in cloud-init source package in Yakkety:
  Confirmed
Status in cloud-init source package in Zesty:
  Fix Committed

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