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:

Adding a custom value for fencing timeout in fence_xvm form (optional arguments section) doesn't propagate it into the cluster cib.

The json dump in pcsd.log shows the _res_paramempty_timeout value as empty although it was filled  with a numerical value (I truncated the large lines a little):

I, [2015-04-20T15:10:24.487685 #16046]  INFO -- : Updating fence device
I, [2015-04-20T15:10:24.487983 #16046]  INFO -- : {"resource_id"=>"Fencing", "resource_type"=>"fence_xvm", "_res_param ... _action"=>"", "_res_paramempty_timeout"=>"", "_res_paramne_delay"=>"10", "_res_paramem...
I, [2015-04-20T15:10:24.488407 #16046]  INFO -- :  delay=10 pcmk_host_map=virt-041 ... pcmk_host_check=static-list
I, [2015-04-20T15:10:24.488615 #16046]  INFO -- : Running: /usr/sbin/pcs stonith update Fencing delay=10 pcmk_host_map=virt-041 ... pcmk_host_check=static-list


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

pcs-0.9.137-13.el7_1.2.x86_64


> Steps to Reproduce:

1. open a fence_xvm based fencing device form in pcs GUI
2. expand Optional Arguments
3. put an integer into 'timeout' field
4. submit

patch in upstream:
https://github.com/feist/pcs/commit/c843c4251046eef915a9f91173fe0724e5bf3cbe

Before Fix:
[root@rh71-node1 ~]# rpm -q pcs
pcs-0.9.137-13.el7_1.2.x86_64

1. open a fence_xvm based fencing device form in pcs GUI
2. expand Optional Arguments
3. put an integer into 'timeout' field
4. submit
5. page reloads
6. expand Optional Arguments
7. the value is missing in the 'timeout' field



After Fix:
[root@rh71-node1:~]# rpm -q pcs
pcs-0.9.140-1.el7.x86_64

7. The value is present in the 'timeout' field.

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://rhn.redhat.com/errata/RHSA-2015-2290.html