RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

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

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

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