$ 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: /boot/vmlinuz-4.4.0-1001-aws Found kernel: /boot/vmlinuz-4.4.0-1001-aws Updating /boot/grub/menu.lst ... done
** Tags removed: verification-needed ** Tags added: verification-done ** 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: 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. -- 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 appropriate for EC2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1655934/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
