Description of problem: upgrade install leaves the (upgraded) Xen kernel un-bootable Version-Release number of selected component (if applicable): RHEL5.1 to RHEL5.2 beta How reproducible: Execute an upgrade install on a RHEL5.1 install that has both a Xen and non-Xen kernel Steps to Reproduce: 1. 2. 3. Actual results: Booting 'Red Hat .... 2.6.18-84xen)' Root (hd0,0) Filesystem type is ext2fs, partitiion type 0x83 Kernel /vmlinux-2.6.18-84.el5xen ro root=LABEL=/ Error 13: Invalid or unsupported executable format Press any key to continue ... Expected results: Additional info: If I then select the non-xen -84 kernel it comes up fine. I then (from experience) force install the xen kernel rpm -ihv --force kernel-xen-2-xxxxxxxxxx.rpm And then it is fine. This has actually been around since 5.0
In setting up an private yum mirror source (rsynced from porkchop), I noticed that I had to rebuild the repos for VT. yum update would complain that xen was a missing dependancy for xen-libs. Once the repo was rebuild for VT, it could satisfy yum. The tree that I use to do the update install is unpacked from a set of ISO and placed on NFS. Maybe the Cluster rpms don't get updated because I should have rebuild the Cluster and ClusterStorage repos after I unpacked this tree? I will rebuild the repos and then attempt an upgrade install on Node2.
Is this still the case with 5.3? I know there have been some problems lately with the comps files for the various other products causing kernel modules and kernels to get pulled in that otherwise shouldn't.
I probably need to first verify if it was fixed in 5.2 production and/or test the 5.2/5.3 update install as well.
Hi Jeff, upgrades to beta frequently have issues (that we try to have resolved in GA), please let us know if you have an issue upgrading from RHEL 5.1 to RHEL 5.2 GA, or to RHEL 5.3 GA.