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:
When priority is not specified the behavior is not consistent.

Version-Release number of selected component (if applicable):
policycoreutils-2.5-2.el7

How reproducible:
100%

Steps to Reproduce:
have a built module my_module.pp
# semodule -i ./my_module.pp
# semodule -lfull | grep my_module
400 my_module         pp         
# semodule -X 500 -i ./my_module.pp
libsemanage.semanage_direct_install_info: Overriding my_module module at lower priority 400 with module at priority 500.
# semodule -lfull | grep my_module
500 my_module         pp         
400 my_module         pp    
# semodule -d my_module           <------ disables all modules of the name
# semodule -lfull | grep my_module
500 my_module         pp disabled
400 my_module         pp disabled
# semodule -r my_module           <------ removes only module with default prio
# semodule -lfull | grep my_module
500 my_module         pp disabled

Expected results:
semodule -r without priority specified should remove all modules regardless priority

-d intentionally disables all priorities in order not to confuse users:

Enable/disabling of modules is done across all priorities simultaneously to avoid confusion that would likely arise from per priority settings.

While -r works with priorities where 400 is the default used when a priority is not explicitly specified.

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.

https://access.redhat.com/errata/RHSA-2018:0913