Bug 690279

Summary: kickstart with selinux --disabled done not work. Required package not in @base
Product: Red Hat Enterprise Linux 5 Reporter: kent lamb <klamb>
Component: compsAssignee: Tomas Kopecek <tkopecek>
Status: CLOSED WONTFIX QA Contact: Release Test Team <release-test-team>
Severity: high Docs Contact:
Priority: high    
Version: 5.6CC: aparsons, atodorov, bgollahe, cww, joel.kergozou, jpriddy, jwest, luvilla, robin.bowes, simon.reber
Target Milestone: rcKeywords: Regression
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-10-18 15:05:43 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On:    
Bug Blocks: 668957    

Description kent lamb 2011-03-23 19:15:11 UTC
Description of problem:
When kickstarting a rhel5.6 system and setting selinux --disabled while only installing @base, the --disabled option does not work, as it requires 
system-config-securitylevel-tui

Version-Release number of selected component (if applicable):

rhel 5.6
How reproducible:
every time

Steps to Reproduce:
1.kickstart 5.6 with selinux --disabled and @base as the only group
2.
3.
  
Actual results:

selinux is enabled
Expected results:

selinux is disabled
Additional info:
https://www.redhat.com/archives/rhelv5-list/2011-January/msg00066.html

Comment 1 Ondrej Vasik 2011-03-23 20:04:29 UTC
Basesystem is just dependency metapackage with no content. I'm not really sure where to reassign that, probably comps or distribution. I'll go with distribution.

Comment 2 Robin Bowes 2011-05-23 09:55:17 UTC
This has bitten me too (I use SELINUX=permissive, rather than =disabled).

Comment 7 Tomas Kopecek 2011-10-12 10:40:48 UTC
Is this bug reported to be present in 5.7? I can't reproduce it.

Comment 8 Alexander Todorov 2011-10-18 14:55:37 UTC
Tested with:

selinux --disabled
%packages --ignoremissing
@core


and 

selinux --disabled
%packages --ignoremissing
@Base


on RHEL 5.7. In both cases SELinux was disabled and system-config-securitylevel-tui was installed. Can't reproduce.

Comment 9 RHEL Program Management 2011-10-18 15:05:43 UTC
Quality Engineering Management has reviewed and declined this request.  You may
appeal this decision by reopening this request.

Comment 10 Joel Kergozou 2012-03-04 18:29:52 UTC
Hi all !

To correctly test it, you should try with :

selinux --disabled
%packages --ignoremissing --nobase
@core

Since at least 5.7 (may be earlier), the "Base" group is implicitly selected by %packages (as the "Core" group).

I have tried the following :

#
selinux --disabled 
%packages --nobase
@Core
#
And at end of installation, selinux is set to 'enforcing'


Tried the following :

#
selinux --disabled 
%packages --nobase
@Core
system-config-securitylevel-tui 
#

And then, selinux is set to 'disabled'.

One solution would be to add "system-config-securitylevel-tui" package in the "Core" group (it is needed for "lokkit" ...).

So, I think this bug should be reopened.

Thanks.