Red Hat Bugzilla – Bug 578205
kickstarting on ppc fails due '/usr/sbin/merge-rd.sh' wrong parameters
Last modified: 2010-07-12 23:17:18 EDT
Description of problem:
i'm not able to kickstart rhel5.5 for ppc from satellite
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. install satellite 5.3.0, update from rhn prod
2. reregister and reactivate system against rhn.webqa
3. sync rhel-ppc-server-5 and its rhn-tools from webqa
4. create rhel5-u5 kickstart profile for ppc
5. register ppc machine and enable provisioning
6. start provisioning of ppc machine
7. on ppc run 'rhn_check -vv'
kickstarting will start
failed event - https://dell-pe700-01.rhts.eng.bos.redhat.com/network/systems/details/history/event.pxt?sid=1000010044&hid=211
Within the event I see "Error creating the new RAM disk". Where did you see the "/usr/sbin/merge-rd.sh' error?
on 'rhn_check -vv' output
Created attachment 403589 [details]
Ok, Finally i've figured this out. The problem is that for ppc and s390x we use a different initrd image than /boot/initrd.img. For ppc we use ramdisk.image.gz.
However spacewalk-koan does not realize this and always tries to use /boot/initrd.img.
Basically file preservation is broken for ppc and s390(x) and has been broken since Satellite 5.3 shipped.
I will open up a bug for this.
If i turn off file preservation on the kickstart you are using it gets past the rhn_check and reboots the machine. However for me it seemed to hang after this and I couldn't seem to get it back into a sane state. If i tried to reprovision to RHEL 5u4 or u5 using rhts it would traceback at anaconda.
*** This bug has been marked as a duplicate of bug 578650 ***