Bug 246531 - kickstart sanity checker not catching selinux optoins
Summary: kickstart sanity checker not catching selinux optoins
Alias: None
Product: Red Hat Satellite 5
Classification: Red Hat
Component: Provisioning   
(Show other bugs)
Version: 420
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Mike McCune
QA Contact: Red Hat Satellite QA List
Depends On:
Blocks: 462714
TreeView+ depends on / blocked
Reported: 2007-07-02 20:58 UTC by marc skinner
Modified: 2011-01-05 22:28 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2011-01-05 22:28:20 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description marc skinner 2007-07-02 20:58:20 UTC
Description of problem:

RHSS 4.2.1embedded

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.

Comment 1 Clifford Perry 2011-01-05 22:28:20 UTC
The RHN Satellite 4.x and RHN Proxy 4.x products have reached their end of life. Please see:

Satellite 4 EOL Errata
 - https://rhn.redhat.com/errata/RHSA-2011-0001.html

RHN Proxy 4 EOL Errata
 - https://rhn.redhat.com/errata/RHSA-2011-0002.html

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. 


Note You need to log in before you can comment on or make changes to this bug.