RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
If SELinux is disabled completely during install, the directory /etc/selinux/targeted/logins/ is not there at all. I don't think that's right as this imposes more application logic for all 3rd party applications creating selinux user contexts and leads to bugs https://bugzilla.redhat.com/show_bug.cgi?id=914433

Moreover, when SELinux is disabled completely

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


Steps to Reproduce:
1. install a RHEL box with selinux disabled 
2. ls /etc/selinux/targeted/logins/

  
Actual results:
not there

Expected results:
the directory should always be there IMO. At least it should be recreated during autorelabel.

Additional info:

What does

# rpm -q selinux-policy-targeted

On my system:

# rpm -qf /etc/selinux/targeted/logins/
selinux-policy-targeted-3.7.19-195.el6_4.1.noarch

The dir should be there.

Created attachment 703162 [details]
Peer1 standard anakonda-ks.cfg

A few servers at work are managed servers in Peer1 UK datacentre. Peer1 standard anakonda-ks.cfg contains the following lines:

selinux --disabled
-selinux-policy-targeted

So, this issue may affect quite a few RHEL 6.4 installations.

Ah, I see, you manually removed selinux-policy-targeted from the kickstart. I missed this point in the original bug report. 

Then we should make sure SSSD is robust against this case (which we did upstream recenly). Mirek, feel free to close as NOTABUG, then. Sorry for the time you spent on this issue.

Probably should be a bug against sssd.