Red Hat Bugzilla – Bug 1337192
semodule: provide better documentation for behavior across operations with modules
Last modified: 2018-04-10 12:37:28 EDT
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