Description of problem: ------------------------- * Is installing a RHS2.0 node over the network via kickstart supported or atleast considered a proper method of installation ? * This is because there is no label named 'linux' defined in 'isolinux/isolinux.cfg' in a RHS2.0 ISO. * The isloinux.cfg configuration is as following : <snip> default install prompt 1 timeout 30 display boot.msg F1 boot.msg label install kernel vmlinuz append initrd=initrd.img ks=file:/ks.cfg quiet label rescue kernel vmlinuz append initrd=initrd.img rescue label local localboot 1 label memtest86 kernel memtest append - </snip> I dont see our documentation talking anything about kickstarting with an RHS2.0 ISO. So a user who tries to do a kickstart (assuming it will work as a normal RHEL ISO) will normally use something like 'linux ks=<URL>/ks.cfg' to try out a kickstart installation which will ofcourse error out with the message "Could not find kernel image: linux'. Was the isolinux.cfg edited to omit out the 'linux' label on purpose ? Or am I overlooking something ? Version-Release number of selected component (if applicable): -------------------------------------------------------------- * RHS2.0 How reproducible: ------------------ * Always Steps to Reproduce: --------------------- 1. Boot the machine with an RHS2.0 ISO to do a normal or network install. 2. Enter 'linux <further arguments>' 3. The installer will error out with the message "Could not find kernel image: linux'. Actual results: --------------- * The installer errors out with the message : "Could not find kernel image: linux'. Expected results: ------------------ * The installer should continue with the install taking 'linux' as a proper argument.
Verified on RHS-2.1-20130806.n.2-RHS-x86_64-DVD.iso, isolinux.cfg now has: label linux kernel vmlinuz append initrd=initrd.img ks=file:/ks.cfg quiet asknetwork
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2013-1262.html