[Bug 1005551] Re: update-grub-legacy-ec2 ignores kernels named -generic
** No longer affects: linux-lts-quantal (Ubuntu) ** No longer affects: linux-lts-quantal (Ubuntu Precise) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1005551 Title: update-grub-legacy-ec2 ignores kernels named -generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1005551/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1005551] Re: update-grub-legacy-ec2 ignores kernels named -generic
** Branch linked: lp:~ubuntu-branches/ubuntu/precise/cloud-init/precise- proposed ** Branch linked: lp:~ubuntu-branches/ubuntu/precise/cloud-init/precise- updates -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1005551 Title: update-grub-legacy-ec2 ignores kernels named -generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1005551/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1005551] Re: update-grub-legacy-ec2 ignores kernels named -generic
This bug was fixed in the package cloud-init - 0.6.3-0ubuntu1.5 --- cloud-init (0.6.3-0ubuntu1.5) precise-proposed; urgency=low * debian/update-grub-legacy-ec2: consider kernels bootable on ec2 that are named -generic, in addition to -virtual. This fixes a problem where the kernels installed by linux-lts-quantal were not added to /boot/grub/menu.lst (LP: #1005551) * debian/patches/lp-1077020-fix-ca-certificates-blanklines.patch: fix adding of empty lines in ca-certificates file (LP: #1077020) * debian/patches/lp-1031065-nonet-not-start-networking.patch: do not 'start networking' in cloud-init-nonet upstart job. Doing so can cause networking to be started earlier than it should be. Instead, add a cloud-init-container job that runs only in a container and emits net-device-added (LP: #1031065). * debian/patches/lp-1037567-add-config-drive-v2-support.conf: backport support for config-drive-v2 which is part of Openstack Nova in Folsom and later. (LP: #1037567) (LP: #1100545) -- Scott MoserWed, 16 Jan 2013 19:37:57 -0500 ** Changed in: cloud-init (Ubuntu Precise) 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/1005551 Title: update-grub-legacy-ec2 ignores kernels named -generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1005551/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1005551] Re: update-grub-legacy-ec2 ignores kernels named -generic
Verified using latest precise released images in us-east-1 EC2. # ami-0145d268 us-east-1/ebs/ubuntu-precise-12.04-amd64-server-20130204 $ ec2metadata --ami-id ami-0145d268 $ ec2metadata --availability-zone us-east-1b $ dpkg-query --show grub-legacy-ec2 grub-legacy-ec2 0.6.3-0ubuntu1.4 $ sudo apt-get install linux-generic-lts-quantal -y -q $ grep "3.5.[0-9]" /boot/grub/menu.lst || echo NOT_FOUND NOT_FOUND $ ls /boot/vmlinuz-3.* /boot/vmlinuz-3.2.0-37-virtual /boot/vmlinuz-3.5.0-23-generic $ echo "deb http://archive.ubuntu.com/ubuntu precise-proposed main" | sudo tee /etc/apt/sources.list.d/proposed.list $ sudo apt-get update $ sudo apt-get install grub-legacy-ec2 $ dpkg-query --show grub-legacy-ec2 grub-legacy-ec2 0.6.3-0ubuntu1.5 $ grep "^title.*3.5.[0-9]" /boot/grub/menu.lst || echo NOT_FOUND titleUbuntu 12.04.2 LTS, kernel 3.5.0-23-generic titleUbuntu 12.04.2 LTS, kernel 3.5.0-23-generic (recovery mode) ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1005551 Title: update-grub-legacy-ec2 ignores kernels named -generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1005551/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1005551] Re: update-grub-legacy-ec2 ignores kernels named -generic
** Description changed: == Begin SRU Information == [General Description] Amazon's EC2 is a xen based cloud platform, the bootloader that is used is 'pvgrub'. pvgrub runs inside a xen instance, reads a /boot/grub/menu.lst file, and loads the kernels specified there. It does not support grub2 style configuration (/boot/grub/grub.cfg). Thus, we have installed inside cloud-images, a package named 'grub-legacy-ec2' that maintains /boot/grub/menu.lst. grub-legacy-ec2 does not simply assume all kernels are candidates for inclusion in /boot/grub/menu.lst. Instead, it has some very basic whitelist metrics. Those previously required a kernel to end in '-virtual'. In the development cycle of 12.10, the -virtual kernel went away. It is now simply a -generic kernel with a subset of modules. [Impact] - In 12.04, it is now supported to run a 12.10 "backports kernel". These new kernels will be named in the newer fashion, and will end in '-generic', rather than '-virtual'. As a result, grub-legacy-ec2's whitelist will not write entries for these kernels to /boot/grub/menu.lst. + In 12.04, it is now supported to run a 12.10 "enablement kernel" (https://wiki.ubuntu.com/Kernel/LTSEnablementStack). These new kernels will be named in the newer fashion, and will end in '-generic', rather than '-virtual'. As a result, grub-legacy-ec2's whitelist will not write entries for these kernels to /boot/grub/menu.lst. The end result is that the user who installs these kernels will not be able to easily boot them on EC2 (or other xen guest). [Test Case] - * Boot a cloud instance or cloud image - * install a backports kernel - * verify that kernel new kernel is included in /boot/grub/menu.lst -Previously the kernel would not be included there. + * Boot a cloud instance or cloud image +The daily build of a EC2 AMI id at http://cloud-images.ubuntu.com/server/precise/current/ is fine. + * install a backports kernel +sudo apt-get install linux-generic-lts-quantal + * verify that kernel new kernel is included in /boot/grub/menu.lst + Previously the kernel would not be included there. +Previously: +$ grep "3.5.[0-9]" /boot/grub/menu.lst || echo NOT_FOUND +NOT_FOUND + +But with new update-grub, it will be. +# enable proposed +$ echo "deb http://archive.ubuntu.com/ubuntu precise-proposed main" | + sudo tee /etc/apt/sources.list.d/proposed.list +$ sudo apt-get update +$ sudo apt-get install grub-legacy-ec2 +$ sudo update-grub-legacy-ec2 +$ grep "3.5.[0-9]" /boot/grub/menu.lst || echo NOT_FOUND +titleUbuntu 12.04.2 LTS, kernel 3.5.0-24-generic +kernel /boot/vmlinuz-3.5.0-24-generic root=LABEL=cloudimg-rootfs ro console=hvc0 +... [Regression Potential] The biggest potential for regression would be in writing an entry to /boot/grub/menu.lst for a kernel that would not boot. There is protection against this in the included patch by checking the version number as well as the name. That amounts to: - dpkg --compare-versions ${ver_flavor%-generic} ge 3.4.0-3 && return 0;; + dpkg --compare-versions ${ver_flavor%-generic} ge 3.4.0-3 && return 0;; where 'ver_flavor' is the version as found in the file name of the kernel (ie, /boot/vmlinux-2.6.35-13-generic). == End SRU Information == Quantal stopped booting on EC2 around 2012-05-25. ben@padfoot:~$ ec2-get-console-output -i i-75727213 Required parameter 'INSTANCE' missing (-h for usage) ben@padfoot:~$ ec2-get-console-output i-75727213 i-75727213 2012-05-28T14:17:49+ Xen Minimal OS! start_info: 0xb1(VA) nr_pages: 0x6a400 shared_inf: 0x001a5000(MA) pt_base: 0xb13000(VA) nr_pt_frames: 0x9 mfn_list: 0x967000(VA) mod_start: 0x0(VA) mod_len: 0 flags: 0x0 cmd_line: root=/dev/sda1 ro 4 stack: 0x946780-0x966780 MM: Init _text: 0x0(VA) _etext: 0x61e65(VA) _erodata: 0x76000(VA) _edata: 0x7b6d4(VA) stack start: 0x946780(VA) _end: 0x966d34(VA) start_pfn: b1f max_pfn: 6a400 Mapping memory range 0xc0 - 0x6a40 setting 0x0-0x76000 readonly skipped 0x1000 MM: Initialise page allocator for e6c000(e6c000)-0(6a40) MM: done Demand map pfns at 6a401000-7a401000. Heap resides at 7a402000-ba402000. Initialising timer interface Initialising console ... done. gnttab_table mapped at 0x6a401000. Initialising scheduler Thread "Idle": pointer: 0x7a402008, stack: 0x6a03 Initialising xenbus Thread "xenstore": pointer: 0x7a402478, stack: 0x6a04 Dummy main: start_info=0x966880 Thread "main": pointer: 0x7a4028e8, stack: 0x6a05 "main" "root=/dev/sda1" "ro" "4" vbd 2049 is hd0 *** BLKFRONT for device/vbd/2049 ** backend at /local/domain/0/backend/vbd/126/2049 Failed to read /local/domain/0/backend/vbd/126/2049/feature-barrier. Failed to r
[Bug 1005551] Re: update-grub-legacy-ec2 ignores kernels named -generic
Hello Ben, or anyone else affected, Accepted cloud-init into precise-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/cloud- init/0.6.3-0ubuntu1.5 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: cloud-init (Ubuntu Precise) Status: Confirmed => Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1005551 Title: update-grub-legacy-ec2 ignores kernels named -generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1005551/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1005551] Re: update-grub-legacy-ec2 ignores kernels named -generic
** Description changed: + == Begin SRU Information == + [General Description] + Amazon's EC2 is a xen based cloud platform, the bootloader that is used is 'pvgrub'. pvgrub runs inside a xen instance, reads a /boot/grub/menu.lst file, and loads the kernels specified there. It does not support grub2 style configuration (/boot/grub/grub.cfg). Thus, we have installed inside cloud-images, a package named 'grub-legacy-ec2' that maintains /boot/grub/menu.lst. + + grub-legacy-ec2 does not simply assume all kernels are candidates for + inclusion in /boot/grub/menu.lst. Instead, it has some very basic + whitelist metrics. Those previously required a kernel to end in + '-virtual'. + + In the development cycle of 12.10, the -virtual kernel went away. It is + now simply a -generic kernel with a subset of modules. + + [Impact] + In 12.04, it is now supported to run a 12.10 "backports kernel". These new kernels will be named in the newer fashion, and will end in '-generic', rather than '-virtual'. As a result, grub-legacy-ec2's whitelist will not write entries for these kernels to /boot/grub/menu.lst. + + The end result is that the user who installs these kernels will not be + able to easily boot them on EC2 (or other xen guest). + + [Test Case] + * Boot a cloud instance or cloud image + * install a backports kernel + * verify that kernel new kernel is included in /boot/grub/menu.lst +Previously the kernel would not be included there. + + [Regression Potential] + The biggest potential for regression would be in writing an entry to /boot/grub/menu.lst for a kernel that would not boot. There is protection against this in the included patch by checking the version number as well as the name. + + That amounts to: + dpkg --compare-versions ${ver_flavor%-generic} ge 3.4.0-3 && return 0;; + where 'ver_flavor' is the version as found in the file name of the kernel (ie, /boot/vmlinux-2.6.35-13-generic). + == End SRU Information == + Quantal stopped booting on EC2 around 2012-05-25. ben@padfoot:~$ ec2-get-console-output -i i-75727213 Required parameter 'INSTANCE' missing (-h for usage) ben@padfoot:~$ ec2-get-console-output i-75727213 i-75727213 2012-05-28T14:17:49+ Xen Minimal OS! - start_info: 0xb1(VA) - nr_pages: 0x6a400 - shared_inf: 0x001a5000(MA) - pt_base: 0xb13000(VA) + start_info: 0xb1(VA) + nr_pages: 0x6a400 + shared_inf: 0x001a5000(MA) + pt_base: 0xb13000(VA) nr_pt_frames: 0x9 - mfn_list: 0x967000(VA) -mod_start: 0x0(VA) - mod_len: 0 -flags: 0x0 - cmd_line: root=/dev/sda1 ro 4 - stack: 0x946780-0x966780 + mfn_list: 0x967000(VA) + mod_start: 0x0(VA) + mod_len: 0 + flags: 0x0 + cmd_line: root=/dev/sda1 ro 4 + stack: 0x946780-0x966780 MM: Init - _text: 0x0(VA) - _etext: 0x61e65(VA) -_erodata: 0x76000(VA) - _edata: 0x7b6d4(VA) + _text: 0x0(VA) + _etext: 0x61e65(VA) + _erodata: 0x76000(VA) + _edata: 0x7b6d4(VA) stack start: 0x946780(VA) -_end: 0x966d34(VA) - start_pfn: b1f - max_pfn: 6a400 + _end: 0x966d34(VA) + start_pfn: b1f + max_pfn: 6a400 Mapping memory range 0xc0 - 0x6a40 setting 0x0-0x76000 readonly skipped 0x1000 MM: Initialise page allocator for e6c000(e6c000)-0(6a40) MM: done Demand map pfns at 6a401000-7a401000. Heap resides at 7a402000-ba402000. Initialising timer interface Initialising console ... done. gnttab_table mapped at 0x6a401000. Initialising scheduler Thread "Idle": pointer: 0x7a402008, stack: 0x6a03 Initialising xenbus Thread "xenstore": pointer: 0x7a402478, stack: 0x6a04 Dummy main: start_info=0x966880 Thread "main": pointer: 0x7a4028e8, stack: 0x6a05 - "main" "root=/dev/sda1" "ro" "4" + "main" "root=/dev/sda1" "ro" "4" vbd 2049 is hd0 *** BLKFRONT for device/vbd/2049 ** - backend at /local/domain/0/backend/vbd/126/2049 Failed to read /local/domain/0/backend/vbd/126/2049/feature-barrier. Failed to read /local/domain/0/backend/vbd/126/2049/feature-flush-cache. 16777216 sectors of 0 bytes ** vbd 2050 is hd1 *** BLKFRONT for device/vbd/2050 ** - backend at /local/domain/0/backend/vbd/126/2050 Failed to read /local/domain/0/backend/vbd/126/2050/feature-barrier. Failed to read /local/domain/0/backend/vbd/126/2050/feature-flush-cache. 312705024 sectors of 0 bytes ** vbd 2051 is hd2 *** BLKFRONT for device/vbd/2051 ** - backend at /local/domain/0/backend/vbd/126/2051 Failed to read /local/domain/0/backend/vbd/126/2051/feature-barrier. Failed to read /local/domain/0/backend/vbd/126/2051/feature-flush-cache. 1835008 sectors of 0 bytes ** [H[J Booting 'Ubuntu quantal (development branch), memtest86+' root (hd0) - Filesystem ty
[Bug 1005551] Re: update-grub-legacy-ec2 ignores kernels named -generic
just an update, I uploaded cloud-init with this fix to precise-proposed on 2013-01-31. We're just still waiting on SRU team review. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1005551 Title: update-grub-legacy-ec2 ignores kernels named -generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1005551/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1005551] Re: update-grub-legacy-ec2 ignores kernels named -generic
Przygotowanie do zastąpienia grub-legacy-ec2 0.6.3-0ubuntu1.4 (wykorzystując .../grub-legacy-ec2_0.6.3-0ubuntu1.5~ppa0_all.deb) ... Leaving 'diversion of /usr/sbin/grub-set-default to /usr/sbin/grub-set-default.real by grub-legacy-ec2' Rozpakowanie pakietu zastępującego grub-legacy-ec2 ... Przetwarzanie wyzwalaczy dla man-db... Konfigurowanie isc-dhcp-common (4.1.ESV-R4-0ubuntu5.6) ... Konfigurowanie isc-dhcp-client (4.1.ESV-R4-0ubuntu5.6) ... Konfigurowanie dhcp3-client (4.1.ESV-R4-0ubuntu5.6) ... Konfigurowanie dhcp3-common (4.1.ESV-R4-0ubuntu5.6) ... Konfigurowanie grub-legacy-ec2 (0.6.3-0ubuntu1.5~ppa0) ... 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: /boot/vmlinuz-3.5.0-22-generic Found kernel: /boot/vmlinuz-3.5.0-21-generic Found kernel: /boot/vmlinuz-3.2.0-36-virtual Found kernel: /boot/vmlinuz-3.2.0-35-virtual Found kernel: /boot/vmlinuz-3.2.0-23-virtual Replacing config file /run/grub/menu.lst with new version Updating /boot/grub/menu.lst ... done so it works fine for me -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1005551 Title: update-grub-legacy-ec2 ignores kernels named -generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1005551/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1005551] Re: update-grub-legacy-ec2 ignores kernels named -generic
I've committed changes for this in a precise branch at lp:~smoser/ubuntu/precise/cloud-init/sru . I have a ppa build of that at https://launchpad.net/~smoser/+archive/cloud-init-test/ . Any testing on that would be appreciated. The plan is to move SRU this as soon as the current SRU moves to -updates. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1005551 Title: update-grub-legacy-ec2 ignores kernels named -generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1005551/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1005551] Re: update-grub-legacy-ec2 ignores kernels named -generic
** Branch linked: lp:~smoser/ubuntu/precise/cloud-init/sru -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1005551 Title: update-grub-legacy-ec2 ignores kernels named -generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1005551/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1005551] Re: update-grub-legacy-ec2 ignores kernels named -generic
** Summary changed: - Quantal does not boot on EC2 + update-grub-legacy-ec2 ignores kernels named -generic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1005551 Title: update-grub-legacy-ec2 ignores kernels named -generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1005551/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs