Bug 1465824

Summary: RPM macros for Independent Product Policy need improvements
Product: Red Hat Enterprise Linux 7 Reporter: Lukas Vrabec <lvrabec>
Component: selinux-policyAssignee: Lukas Vrabec <lvrabec>
Status: CLOSED ERRATA QA Contact: Milos Malik <mmalik>
Severity: high Docs Contact:
Priority: high    
Version: 7.5CC: jreznik, ksrot, lvrabec, mgrepl, mjahoda, mmalik, plautrba, pvrabec, rkratky, ssekidde
Target Milestone: rcKeywords: Tracking
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1380854 Environment:
Last Closed: 2018-04-10 12:32:41 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1380854, 1393066    
Bug Blocks: 1377248    

Comment 3 Milos Malik 2018-02-13 10:43:44 UTC
The echo vs. /bin/echo issue is fixed now, but ...

the selinux_modules_uninstall macro is able to take [-s <policytype>] as parameter, but semodule always removes the policy module from current policy store. If selinux_modules_uninstall macro was executed under targeted policy with "-s mls" it would remove the policy module from targeted policy store but it would leave the policy module in the mls store.

Comment 5 Milos Malik 2018-02-19 09:31:05 UTC
After discussion with Lukas Vrabec, we agreed that this bug will be switched to VERIFIED and that following issue will be addressed in a new bug:

The selinux_modules_uninstall macro is able to take [-s <policytype>] as parameter, but semodule always removes the policy module from current policy store. If selinux_modules_uninstall macro was executed under targeted policy with "-s mls" it would remove the policy module from targeted policy store but it would leave the policy module in the mls store.

Comment 6 Milos Malik 2018-02-19 09:37:59 UTC
The new bug is BZ#1546664.

Comment 9 errata-xmlrpc 2018-04-10 12:32:41 UTC
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/RHBA-2018:0763