Hide Forgot
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
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.
This has bitten me too (I use SELINUX=permissive, rather than =disabled).
Is this bug reported to be present in 5.7? I can't reproduce it.
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.
Quality Engineering Management has reviewed and declined this request. You may appeal this decision by reopening this request.
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.