Red Hat Bugzilla – Bug 246531
kickstart sanity checker not catching selinux optoins
Last modified: 2011-01-05 17:28:20 EST
Description of problem:
I cloned a working RHEL4U5 kickstart profile and then renamed it to RHEL3U8.
Changed the OS version and patchset from RHEL4U5 to RHEL3U8. It appears that no
sanity checking was done to remove the "selinux --permissive" statement that
isn't supported in the RHEL3 anaconda installer. Thus all kickstarts with that
profile aborted at installation. I was able to fix this, by forcing the gui to
rebuild the kickstart file, that removed the selinux line from the file and
fixed the issue.
I'm guessing we just need to check the sanity checker after the OS level is
changed, specifically for RHEL4/5 to RHEL3/2.1 for kickstart advanced features
such as SELINUX.
The RHN Satellite 4.x and RHN Proxy 4.x products have reached their end of life. Please see:
Satellite 4 EOL Errata
RHN Proxy 4 EOL Errata
This bugzilla was reported for a product which is no longer supported. As such we are closing this bugzilla out. If you feel this bug report should be reviewed again since it is valid for a currently supported product version, then please feel free to re-open this bug report.