This bug was fixed in the package cloud-init - 0.7.5-0ubuntu1.22
---
cloud-init (0.7.5-0ubuntu1.22) trusty; urgency=medium
* debian/update-grub-legacy-ec2:
- Correctly detect kernels ending in -aws as kernels that can boot on EC2
(LP: #1655934)
- Consider kernels with
I have verified that cloud-init (0.7.5-0ubuntu1.22) in trusty -proposed
does fix the problem.
** Tags removed: verification-needed
** Tags added: verification-done-trusty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hello Dan, or anyone else affected,
Accepted cloud-init into trusty-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/cloud-
init/0.7.5-0ubuntu1.22 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package. See
I'd like to revisit the way this was fixed in {X,Y,Z} and will need to
be fixed in T -- which was to add "-aws" to update-grub-legacy-ec2's
whitelist of bootable kernel package names.
We'd like to be able to construct additional EC2-target kernel flavors
with other (arbitrary) names, without
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)
** Changed in: cloud-init (Ubuntu Zesty)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1655934
Title:
update-grub-legacy-ec2 should detect -aws kernels
This bug was fixed in the package cloud-init - 0.7.9-0ubuntu1~16.10.1
---
cloud-init (0.7.9-0ubuntu1~16.10.1) yakkety; urgency=medium
* debian/copyright: update License field to include Apache-2.0
* debian/update-grub-legacy-ec2: fix to include kernels whose config
has
** Tags removed: verification-needed
** Tags added: verification-done-xenial verification-done-yakkety
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1655934
Title:
update-grub-legacy-ec2 should
## launched a yakkety instance
$ cat /etc/cloud/build.info
build_name: server
serial: 20170207
$ lsb_release -sc
yakkety
## Enable proposed
$ rel=$(lsb_release -sc)
$ line=$(awk '$1 == "deb" && $2 ~ /ubuntu.com/ {
printf("%s %s %s-proposed main universe\n", $1, $2, rel); exit(0) };
'
Hello Dan, or anyone else affected,
Accepted cloud-init into yakkety-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/cloud-
init/0.7.9-0ubuntu1~16.10.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package.
** Changed in: cloud-init (Ubuntu Xenial)
Importance: Undecided => Medium
** Changed in: cloud-init (Ubuntu Yakkety)
Importance: Undecided => Medium
** Changed in: cloud-init (Ubuntu Zesty)
Importance: Undecided => Medium
--
You received this bug notification because you are a member
** Description changed:
[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:
** 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
This bug was fixed in the package cloud-init - 0.7.8-49-g9e904bb-
0ubuntu1~16.04.4
---
cloud-init (0.7.8-49-g9e904bb-0ubuntu1~16.04.4) xenial; urgency=medium
* debian/update-grub-legacy-ec2:
- Correctly detect kernels ending in -aws as kernels that can boot on EC2
(LP:
$ sudo update-grub-legacy-ec2
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 ...
Found kernel:
** Changed in: cloud-init (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1655934
Title:
update-grub-legacy-ec2 should detect -aws kernels as
Hello Dan, or anyone else affected,
Accepted cloud-init into xenial-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/cloud-init/0.7.8-49
-g9e904bb-0ubuntu1~16.04.4 in a few hours, and then in the -proposed
repository.
Please help us by testing this
** Changed in: cloud-init (Ubuntu)
Status: Fix Released => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1655934
Title:
update-grub-legacy-ec2 should detect -aws kernels as
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
** Description changed:
- Currently, it will detect -ec2 kernels, but we also need it to detect
- -aws kernels.
+ [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
** Also affects: cloud-init (Ubuntu Xenial)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1655934
Title:
update-grub-legacy-ec2 should detect -aws
21 matches
Mail list logo
