Hide Forgot
Created attachment 525665 [details] The kickstart file Description of problem: I need to automatically install some 32bit packages into x86_64 systems when deploying RHEL x86_64. When I add these packages name(not include version, arch and extension name of the full package name) into kickstart file, the installer still only install the 64bit version. the 32bit version isn't installed. We know that every package has 32bit and 64bit version listed in the /Packages directory of the OS image. Maybe the automatic installation of 32bit packages can be implemented via adding the full package name into ks file. But my ks file need to be applied in many RHEL versions, such as RHEL 6.0, RHEL 6.1, and subsequent RHEL 6.2. The package version maybe change in different RHEL release. How I install 32bit packages into x86_64 system automatically when deploying RHEL x86_64? Version-Release number of selected component (if applicable): anaconda 13.21.117 for x86_64 How reproducible: Always Steps to Reproduce: Add the package name into ks file, then install RHEL with the ks file. Actual results: The 64bit version of the package will be installed. But the 32bit verion will not be installed. Expected results: All the 32bit and 64bit version of specified package can be installed into x86_64 system automatically when deploying RHEL x86_64. Additional info:
Well, it should be in the installation guide in this section: http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html-single/Installation_Guide/index.html#s1-kickstart2-packageselection As of RHEL 6.0, you now have to specify 32-bit packages on 64-bit systems explicitly. Let's say you want both glibc packages on your 64-bit system. The following %packages block demonstrates that: %packages glibc glibc.i686 %end Most users should find it sufficient to add the lines for the 32-bit packages they want at the end of the %packages section generated for them during installation.
The Installation Guide for 6.2 has already entered the translation stage. To fix this in time for the 6.2 release, we would need an exception from the PM, please. Otherwise, we'll be sure to fix it for 6.3.
Thanks for reporting this, Jack. For the next edition of the guide, I've inserted a new paragraph at the link David provided in Comment 2 incorporating his explanation.
This bug is now fixed and available as part of the Red Hat Enterprise Linux 6.3 release on http://docs.redhat.com/. Setting to CLOSED > CURRENTRELEASE.