Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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 you do run for example 'semanage permissive -a permissive' an invalid te file will be generated a left in /var/lib/selinux (I think) and then if you try to run
'semanage permissive -a <type>' again it will fail because it tries to compile the bad te file previously generated.
Version-Release number of selected component (if applicable):
policycoreutils-python-2.0.83-19.30.el6.x86_64
How reproducible:
Steps to Reproduce:
1.semanage permissive -a permissive
2.semanage permissive -a secadm_t
3.
Actual results:
step 2 fails because step 1 failed
Expected results:
Additional info:
Comment 2RHEL Program Management
2013-11-10 23:15:12 UTC
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.
Yes, we have
#semanage permissive -a permissive
ValueError: permissive is not a domain type
Comment 5RHEL Program Management
2014-04-23 12:50:57 UTC
This request was evaluated by Red Hat Product Management for
inclusion in a Red Hat Enterprise Linux release. Product
Management has requested further review of this request by
Red Hat Engineering, for potential inclusion in a Red Hat
Enterprise Linux release for currently deployed products.
This request is not yet committed for inclusion in a release.
Now it seems to be broken a bit:
(even without trying the command with nonexisting type before)
# rpm -qa policycoreutils\*
policycoreutils-python-2.0.83-19.41.el6.x86_64
policycoreutils-2.0.83-19.41.el6.x86_64
# semanage permissive -a httpd_t
/usr/sbin/semanage: httpd_t is not a domain type
(In reply to Michal Trunecka from comment #8)
> Now it seems to be broken a bit:
>
> (even without trying the command with nonexisting type before)
>
> # rpm -qa policycoreutils\*
> policycoreutils-python-2.0.83-19.41.el6.x86_64
> policycoreutils-2.0.83-19.41.el6.x86_64
> # semanage permissive -a httpd_t
> /usr/sbin/semanage: httpd_t is not a domain type
strange, it works on Fedora with the same patch. Need to re-check it.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
http://rhn.redhat.com/errata/RHBA-2014-1569.html