I'm marking this fix-released. Maverick images of 20100913 or later
(including grub-pc of 1.98+20100804-4ubuntu6 and cloud-init of
0.5.15-0ubuntu1) will properly install new kernels, and boot into them
on reboot.
This functionality is also present for Maverick instances that are
running on UEC
Marking as won't fix in ec2-init (karmic or previous). Moving
'Confirmed/Wishlist' to cloud-init.
** Changed in: ec2-init (Ubuntu)
Status: Confirmed = Won't Fix
** Changed in: cloud-init (Ubuntu)
Importance: Undecided = Wishlist
** Changed in: cloud-init (Ubuntu)
Status: New =
** Also affects: cloud-init (Ubuntu)
Importance: Undecided
Status: New
--
investigate ec2 kernel/ramdisk and apt-upgrade
https://bugs.launchpad.net/bugs/506960
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Given the above, I've done some thought on this. I think the best thing to do
right now is leave this as it is.
'apt-get upgrade' actually performs reasonably well, new kernels with same ABI
are installed, so any changes in modules would be picked upon next reboot.
The one thing I think
Just a note
I realized that the reason updates are prompted for is the presense of the meta
packages. If we remove them, the linux-image packages will still be present,
but dont get upgraded. Ie:
linux-image-2.6.32-11-virtual
linux-image-2.6.32-301-ec2
will still be around. Those packages
Seems like a good solution to me.
--
investigate ec2 kernel/ramdisk and apt-upgrade
https://bugs.launchpad.net/bugs/506960
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
** Branch linked: lp:~ubuntu-on-ec2/vmbuilder/automated-ec2-builds
--
investigate ec2 kernel/ramdisk and apt-upgrade
https://bugs.launchpad.net/bugs/506960
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
More discussion on this in IRC. Eric Hammond pointed out that with EBS
volumes, you can actually stop the instance, modify the kernel and
ramdisk attribute and boot the instance with new kerne/ramdisk.
This would actually provide a usable mechanism for updating the kernel
in an EBS volume.
I
