Description of problem: rhel6 -> rhel5 provisioning not working, because old yaboot doesn't recognize rhel6 kernel image as valid elf image. Version-Release number of selected component (if applicable): How reproducible: always on rhel5 ppc Steps to Reproduce: 1. prepare rhel5 ppc machine and satellite-5.4 for provisioning ppc rhel6 2. update it 3. register rhel5 ppc to satellite 4. create kickstart 5. launch this kickstart 6. connect to ppc client console 7. rhel6 kickstart fails 8. boot to linux (boot: linux) 9. download rhel6 yaboot package and extract it and replace files from old yaboot 10. run 'ybin' and reboot again and let machine boot kickstart 11. kernel image is loaded and kickstart launched Actual results: Welcome Welcome to yaboot version 1.3.13 (Red Hat 1.3.13-10.el5) Enter "help" to get some basic usage information boot: kick1287747852 Please wait, loading kernel... /vmlinuz: Not a valid ELF image Expected results: boot: kick1287747852 Please wait, loading kernel... Elf64 kernel loaded... Loading ramdisk... ramdisk loaded at 03600000, size: 30590 Kbytes ..... Additional info:
Roman, Could you please tell us if booting RHEL6 kernel from RHEL5 yaboot should be supported? Thanks.
Can you please try http://rrakus.fedorapeople.org/yaboot-1.3.13-11.el5.ppc.rpm ?
Ok. Let me do some magic with this bug.
Created attachment 455739 [details] Patch allowing to boot relocatable kernels
This request was evaluated by Red Hat Product Management for inclusion in the current release of Red Hat Enterprise Linux. Because the affected component is not scheduled to be updated in the current release, Red Hat is unfortunately unable to address this request at this time. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux.
Patch commited.
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2011-0993.html