Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1403012
Summary: | selinux-policy gets conflicting specs when relabelling | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Michal Jaegermann <michal.jnn> |
Component: | selinux-policy-targeted | Assignee: | Lukas Vrabec <lvrabec> |
Status: | CLOSED DUPLICATE | QA Contact: | Ben Levenson <benl> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 25 | CC: | alan.christopher.jenkins, dwalsh, fedora, joe |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2017-04-24 13:40:05 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: |
Description
Michal Jaegermann
2016-12-08 21:28:56 UTC
*** Bug 1411371 has been marked as a duplicate of this bug. *** I think this is a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1378323 (In reply to Alan Jenkins from comment #2) > I think this is a duplicate of > https://bugzilla.redhat.com/show_bug.cgi?id=1378323 You are right. Only that bugzilla for some reasons distinguish between selinux-policy and selinux-policy-targeted components so it is not finding earlier report if a search was run with a "wrong" component. I am not sure what to do about that. (In reply to Michal Jaegermann from comment #3) > I am not sure what to do about that. Please close this bug as a duplicate of 1378323. You'll find the required UI below the comments field. Thanks! *** This bug has been marked as a duplicate of bug 1378323 *** |