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:


Version-Release number of selected component (if applicable):
policycoreutils-2.0.83-19.12.el6.i686
policycoreutils-python-2.0.83-19.12.el6.i686
policycoreutils-sandbox-2.0.83-19.12.el6.i686
policycoreutils-gui-2.0.83-19.12.el6.i686
policycoreutils-newrole-2.0.83-19.12.el6.i686

How reproducible:
always

Steps to Reproduce:
[root@rhel62 ~]# sestatus 
SELinux status:                 disabled
[root@rhel62 ~]# semanage permissive -l
Traceback (most recent call last):
  File "/usr/sbin/semanage", line 564, in <module>
    process_args(sys.argv[1:])
  File "/usr/sbin/semanage", line 383, in process_args
    OBJECT.list(heading, locallist)
  File "/usr/lib/python2.6/site-packages/seobject.py", line 341, in list
    all = map(lambda y: y["name"], filter(lambda x: x["permissive"], setools.seinfo(setools.TYPE)))
  File "/usr/lib/python2.6/site-packages/setools/__init__.py", line 49, in seinfo
    dict_list = _seinfo.seinfo(setype, name)
RuntimeError: No default policy found.
[root@rhel62 ~]# echo $?
1
[root@rhel62 ~]# 

Expected results:
* either the tool can cope with disabled SELinux and displays permissive domains as expected
* or the tool shows "SELinux is disabled" message as other tools do

Milos can you add the following to the end of semanage to make sure it works.

I don't have a disabled machine to test on.

	except RuntimeError, error:
		errorExit(error.args[1])

It didn't work when error.args[1] was used, but it works when error.args[0] is used.

# tail -n 3 /usr/sbin/semanage 
	except RuntimeError, error:
		errorExit(error.args[0])

# sestatus 
SELinux status:                 disabled
# semanage permissive -l
/usr/sbin/semanage: No default policy found.
#

Great that is what I was looking for.

Fixed in policycoreutils-2.0.83-19.13.el6

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-2011-1637.html