Red Hat Bugzilla – Bug 820228
Adding some packages in SE templates could upgrade the kernel at ec2 and fails to boot
Last modified: 2012-12-10 16:53:50 EST
Description of problem:
I added rhev-agent package in SE template and the kernel on ec2 instance failed to boot.
Agreed the rhev-agent package is required only if working with RHEV provider,
Adding rhev-agent, kernel changed to : 2.6.18-308
Actual kernel required : 2.6.18-307.el5xen
May be this can go in as a documentation or Technical Notes entry.
Version-Release number of selected component (if applicable):
Build : rc1
Occurred when adding the rhev-agent package to the SE-template for RHEL5 OS.
There could also be other packages which could upgrade the kernel and render the image useless.
Steps to Reproduce:
Filesystem type is ext2fs, using whole disk
kernel /boot/vmlinuz-2.6.18-308.4.1.el5 ro root=LABEL=/
ERROR Invalid kernel: xc_dom_probe_bzimage_kernel: boot protocol too old (0204)
xc_dom_bzimageloader.c:351: panic: xc_dom_probe_bzimage_kernel: boot protocol too old (0204)
ERROR Invalid kernel: xc_dom_parse_elf_kernel: ELF image has no shstrtab
xc_dom_elfloader.c:246: panic: xc_dom_parse_elf_kernel: ELF image has no shstrtab
xc_dom_parse_image returned -1
Error 9: Unknown boot failure
upgrading the kernel of ec2 instances outside of RHUI is not supported.. A tech note would be a good idea, more doc is better than less.
Release Note added. Link:
Apart from the release note in comment #2, is there any other documentation needed for this particular bug?
Added the following admonition to exporting system templates from System Engine:
Adding certain packages in CloudForms System Engine templates can upgrade the kernel on EC2 images, which can cause boot failure and render the image useless. Red Hat does not support upgrading the kernel of EC2 instances outside of <application>Red Hat Update Infrastructure</application>.
This documentation has now been dropped to translation ahead of publication. For any further issues, please open a new a bug.
This document is now publicly available on access.redhat.com. For any further issues, please raise a new bug.