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:
When running a ccs -h <hostname> --setfencedaemon post_fail_delay=(X)
and a ccs -h <hostname> --setfencedaemon post_join_delay=(X)
right after each other as written in the RHEL CS Guide 6.3 (Page 63)
One attribute will overwrite the other without letting the user know,
i.e. only the last attribute is set, there is no additional feedback or exit
code. This is easily reproduced, when doing so in a single line like
ccs -h <hostname> --setfencedaemon post_fail_delay=(X) post_join_delay=(X)

then it works, but this is not documented.

Version-Release number of selected component (if applicable):

RHEL Cluster Suite 6.3 

How reproducible:
See Description

Steps to Reproduce:
1.ccs -h <hostname> --setfencedaemon post_fail_delay=(X)
2.ccs -h <hostname> --setfencedaemon post_join_delay=(X)
3.check cluster.conf - last command overwrite the other attribute in the cluster.con

  
Actual results:


Expected results:
have cluster.conf contain both or give some feedback that attributes are being
overwritten.

Additional info:

Our Documentation snippet is wrong or ccs should be fixed:

T o configure a value for the post_fail_delay attribute, execute the following command:
ccs -h host --setfencedaemon post_fail_delay=value
T he post-join_delay attribute is the number of seconds the fence daemon (fenced) waits
before fencing a node after the node joins the fence domain. T he post_join_delay default value
is 3. A typical setting for post_join_delay is between 20 and 30 seconds, but can vary according
to cluster and network performance.
T o configure a value for the post_join attribute, execute the following command:
ccs -h host --setfencedaemon post_join_delay=value
Note
For more information about the post_join_delay and post_fail_delay attributes as we


This is straight out of our 6.3 Cluster Admin Guide.

c

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

there should be also some feedback from the command line btw, if ccs is overwriting an attribute it would be of some use to give back some alert here