Bug 1717113

Summary:	[packaging] pcs daemon does require "pam" package but doesn't declare so in the spec
Product:	Red Hat Enterprise Linux 8	Reporter:	Jan Pokorný [poki] <jpokorny>
Component:	pcs	Assignee:	Ivan Devat <idevat>
Status:	CLOSED ERRATA	QA Contact:	cluster-qe <cluster-qe>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	8.0	CC:	cfeist, cluster-maint, idevat, mlisik, nhostako, omular, tojeline
Target Milestone:	rc	Keywords:	EasyFix
Target Release:	8.0	Flags:	pm-rhel: mirror+
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	pcs-0.10.2-1.el8	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-11-05 20:40:02 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 Jan Pokorný [poki] 2019-06-04 17:40:54 UTC

This is actually a double violation of the packaging policies(!)

1. something effectively required is not marked so
   (otherwise AttributeError/undefined symbol is imminent)

2. file dropped under the directory possessed with another
   package requires that this other package is required
   (alternatively, the parent hierarchy of directories up
   to filesystem package level can be co-owned)

This will likely render pcs unusable in cut-down containers.

Please fix:
- RHEL 8 line
- RHEL 7 line if 0.10 line is to be used there
- Fedoras

Comment 1 Jan Pokorný [poki] 2019-06-04 17:50:04 UTC

What's worse, using this ultimately hacky way of ctypes, automatic
"Requires:" generator cannot recognized the intention to use that
library in a way it can for static compiled code.

(Out of interest, checked that pacemaker-remote doesn't contain
such dependency on pam, whether requested or implied in said way.
Might be good for have an optional fallback relying on system
libc functions only so that containers don't grow unnecessarily.)

Comment 6 errata-xmlrpc 2019-11-05 20:40:02 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/RHEA-2019:3311