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:
semanage show local customizations to policy even if the is now change against policy default.

Version-Release number of selected component (if applicable):
policycoreutils-2.2.5-20.el7
policycoreutils-2.0.83-24.el6

How reproducible:
100%

Steps to Reproduce:
1. #  semanage boolean -l | grep   git_system_use_cifs
git_system_use_cifs            (off  ,  off)  Determine whether Git system daemon can access cifs file systems.
2. # semanage -o - | grep git_system_use_cifs
3. # setsebool -P git_system_use_cifs on
4. # semanage -o - | grep git_system_use_cifs
boolean -1 git_system_use_cifs
5. # setsebool -P git_system_use_cifs off
6. # semanage -o - | grep git_system_use_cifs
boolean -0 git_system_use_cifs

I think after step 5, there should not be any local customization of git_system_use_cifs.

semanage doesn't do an analysis of the current policy to find out what's the default value. It would be unnecessary expensive. You did a local modification using setsebool and it's shown in the semanage output.