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.
Description of problem:
At the end of 'man ocf_heartbeat_redis' there is a pcs example:
EXAMPLE PCS
The following is an example configuration for a redis resource using pcs(8)
pcs resource create p_redis ocf:heartbeat:redis \
op monitor depth="0" timeout="60s" interval="45s" \
op monitor role="Master" depth="0" timeout="60s" interval="20s" \
op monitor role="Slave" depth="0" timeout="60s" interval="60s" --master
The example advises using --master which does not work in pcs-0.10. The depth option does not work either.
Version-Release number of selected component (if applicable):
resource-agents-4.1.1-33.el8
How reproducible:
always, easily
Steps to Reproduce:
man ocf_heartbeat_redis
Actual results:
Invalid pcs syntax is advised.
Expected results:
Valid pcs syntax is advised.
Additional info:
This has been reported upstream as a pcs issue. Please check it out for more details. https://github.com/ClusterLabs/pcs/issues/214
Comment 3Oyvind Albrigtsen
2020-10-26 16:02:30 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 (resource-agents 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-2021:1736
Description of problem: At the end of 'man ocf_heartbeat_redis' there is a pcs example: EXAMPLE PCS The following is an example configuration for a redis resource using pcs(8) pcs resource create p_redis ocf:heartbeat:redis \ op monitor depth="0" timeout="60s" interval="45s" \ op monitor role="Master" depth="0" timeout="60s" interval="20s" \ op monitor role="Slave" depth="0" timeout="60s" interval="60s" --master The example advises using --master which does not work in pcs-0.10. The depth option does not work either. Version-Release number of selected component (if applicable): resource-agents-4.1.1-33.el8 How reproducible: always, easily Steps to Reproduce: man ocf_heartbeat_redis Actual results: Invalid pcs syntax is advised. Expected results: Valid pcs syntax is advised. Additional info: This has been reported upstream as a pcs issue. Please check it out for more details. https://github.com/ClusterLabs/pcs/issues/214