Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
The upstream pcs 0.9 branch is in a similar life cycle stage as RHEL 7 - it only gets selected backports (almost entirely bug fixes) from the current master branch. In fact, the majority of changes in 0.9 are from Red Hatters backporting fixes needed in RHEL 7. And most of them were already released in 7.8.
Rebasing will take care of the 7.9 RHEL BZs plus a few other minor bugs found and fixed / backported from RHEL 8, would be easier than cherry-picking, and would sync us with the upstream versioning.
[0.9.169] - 2020-04-09
Added
pcs resource relations command shows relations between resources such as ordering constraints, ordering set constraints and relations defined by resource hierarchy (rhbz#1770975)
pcs resource disable can show effects of disabling resources and prevent disabling resources if any other resources would be affected (rhbz#1770973)
Fixed
Do not generate custom DH key if it was not requested by setting its custom length (rhbz#1760434)
Documentation of pcs constraint colocation add (rhbz#1500012)
Empty constraint option are not allowed in pcs constraint order and pcs constraint colocation add commands (rhbz#1500012)
Fixed an issue where some pcs commands could not connect to cluster nodes over IPv6
More fixes for the case when PATH environment variable is not set (rhbz#1671174)
Error messages in cases when cluster is not set up (rhbz#1448569)
Fix documentation and flags regarding bundled/cloned/grouped resources for pcs (resource | stonith) (cleanup | refresh) (rhbz#1759269)
Changed
Pcsd no longer sends Server HTTP header (rhbz#1765606)
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 (pcs bug fix and enhancement update), 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-2020:3964