group.of.nepali.translators team mailing list archive
-
group.of.nepali.translators team
-
Mailing list archive
-
Message #13780
[Bug 1655934] Re: update-grub-legacy-ec2 should detect -aws kernels as appropriate for EC2
This problem occurs when trying to install "other named" kernels on
trusty too.
** Also affects: cloud-init (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: cloud-init (Ubuntu Trusty)
Importance: Undecided => Medium
** Changed in: cloud-init (Ubuntu Trusty)
Assignee: (unassigned) => Dan Watkins (daniel-thewatkins)
--
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 Released
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:
Fix Released
Status in cloud-init source package in Zesty:
Fix Released
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.
Related bugs:
* bug 1379080: update-grub-legacy-ec2 fails to detect xen kernel
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1655934/+subscriptions