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

Description of problem:

In a relabelling, forced after an update, the following message shows up:

filespec_add: conflicting specifications for /usr/sbin/ldconfig and /usr/sbin/sln, using system_u:object_r:bin_t:s0

where two binaries in question actually turn out to be hardlinked.

Version-Release number of selected component (if applicable):
selinux-policy-targeted-3.13.1-224.fc25

Additional info:
The actual error message can be slightly different as it was not logged where I could find it and later vanished from a screen

Comment 1 Alan Jenkins 2017-01-12 16:16:50 UTC

*** Bug 1411371 has been marked as a duplicate of this bug. ***

Comment 2 Alan Jenkins 2017-01-12 16:19:09 UTC

I think this is a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1378323

Comment 3 Michal Jaegermann 2017-01-12 17:29:27 UTC

(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.

Comment 4 Christian Stadelmann 2017-04-24 08:48:10 UTC

(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!

Comment 5 Michal Jaegermann 2017-04-24 13:40:05 UTC


*** This bug has been marked as a duplicate of bug 1378323 ***