Bug 2039883

DevTestResults:

[root@r90-node-01 ~]# rpm -q pcs
pcs-0.11.1-8.el9.x86_64

1. On cluster management page click on "Fence Devices" tab
2. Choose a fence device from a list and click on it, detail of the agent will show up on the right side
3. Click on the "Arguments" tab in the fence device detail
4. Click on the "Edit arguments" button
5. Edit fence device in the "Edit fence device arguments" modal window and click "Save arguments" button
6. Check the "Arguments" tab for the edited arguments

AFTER:
======

[root@virt-516 ~]# rpm -q pcs
pcs-0.11.1-10.el9.x86_64


## Basic cluster setup

[root@virt-516 ~]# pcs status
Cluster name: STSRHTS28904
Cluster Summary:
  * Stack: corosync
  * Current DC: virt-517 (version 2.1.2-4.el9-ada5c3b36e2) - partition with quorum
  * Last updated: Mon Feb 14 14:54:34 2022
  * Last change:  Mon Feb 14 11:17:30 2022 by root via cibadmin on virt-516
  * 2 nodes configured
  * 6 resource instances configured

Node List:
  * Online: [ virt-516 virt-517 ]

Full List of Resources:
  * fence-virt-516	(stonith:fence_xvm):	 Started virt-516
  * fence-virt-517	(stonith:fence_xvm):	 Started virt-517
  * Clone Set: locking-clone [locking]:
    * Started: [ virt-516 virt-517 ]

Daemon Status:
  corosync: active/disabled
  pacemaker: active/disabled
  pcsd: active/enabled


## in web UI

- open new web UI (https://nodename:2224/)
- log in
- Click 'Add existing cluster' button and proceed with the wizard
- Click on the added cluster
- Click on 'Fence Devices'
- Click on one of the fence devices (fence-virt-516 in this case)
- Click on 'Arguments' in the detail of the device
- Click on 'Edit arguments'
	> A window will appear with the devices arguments to be updated, the arguments can be searched and filtered by importance. There is a help message with every argument


- Trying to edit 'delay' argument from 5 to 6 and click 'Save arguments' 
	> Fence device arguments updated sucessfully
before: 
'delay 5'
[root@virt-516 ~]# pcs stonith config fence-virt-516
 Resource: fence-virt-516 (class=stonith type=fence_xvm)
  Attributes: delay=5 pcmk_host_check=static-list pcmk_host_list=virt-516 pcmk_host_map=virt-516:virt-516.cluster-qe.lab.eng.brq.redhat.com
  Operations: monitor interval=60s (fence-virt-516-monitor-interval-60s)

after:
'delay 6'
[root@virt-516 ~]# pcs stonith config fence-virt-516
 Resource: fence-virt-516 (class=stonith type=fence_xvm)
  Attributes: delay=6 pcmk_host_check=static-list pcmk_host_list=virt-516 pcmk_host_map=virt-516:virt-516.cluster-qe.lab.eng.brq.redhat.com
  Operations: monitor interval=60s (fence-virt-516-monitor-interval-60s)

> OK


- Trying to edit multiple arguments at once (delay to 5 and auth to sha1)
> Fence device arguments updated sucessfully
before:
'auth
    sha256
    Default value
delay 6'
[root@virt-516 ~]# pcs stonith config fence-virt-516
 Resource: fence-virt-516 (class=stonith type=fence_xvm)
  Attributes: delay=6 pcmk_host_check=static-list pcmk_host_list=virt-516 pcmk_host_map=virt-516:virt-516.cluster-qe.lab.eng.brq.redhat.com
  Operations: monitor interval=60s (fence-virt-516-monitor-interval-60s)

after:
'auth sha1
delay 5'
[root@virt-516 ~]# pcs stonith config fence-virt-516
 Resource: fence-virt-516 (class=stonith type=fence_xvm)
  Attributes: auth=sha1 delay=5 pcmk_host_check=static-list pcmk_host_list=virt-516 pcmk_host_map=virt-516:virt-516.cluster-qe.lab.eng.brq.redhat.com
  Operations: monitor interval=60s (fence-virt-516-monitor-interval-60s)

> OK


- Trying to change argument to its default value (leaving empty space at auth)
> Fence device arguments updated sucessfully
before:
'auth sha1'
[root@virt-516 ~]# pcs stonith config fence-virt-516
 Resource: fence-virt-516 (class=stonith type=fence_xvm)
  Attributes: auth=sha1 delay=5 pcmk_host_check=static-list pcmk_host_list=virt-516 pcmk_host_map=virt-516:virt-516.cluster-qe.lab.eng.brq.redhat.com
  Operations: monitor interval=60s (fence-virt-516-monitor-interval-60s)

after:
'auth
    sha256
    Default value'
[root@virt-516 ~]# pcs stonith config fence-virt-516
 Resource: fence-virt-516 (class=stonith type=fence_xvm)
  Attributes: delay=5 pcmk_host_check=static-list pcmk_host_list=virt-516 pcmk_host_map=virt-516:virt-516.cluster-qe.lab.eng.brq.redhat.com
  Operations: monitor interval=60s (fence-virt-516-monitor-interval-60s)

> OK: Tried also as multiple arguments change with one argument changing to default


- Trying to change one of the advanced argument (pcmk_status_timeout)
> Fence device arguments updated sucessfully
before:
'pcmk_status_timeout
    60s
    Default value'
[root@virt-516 ~]# pcs stonith config fence-virt-516 
 Resource: fence-virt-516 (class=stonith type=fence_xvm)
  Attributes: delay=5 pcmk_host_check=static-list pcmk_host_list=virt-516 pcmk_host_map=virt-516:virt-516.cluster-qe.lab.eng.brq.redhat.com
  Operations: monitor interval=60s (fence-virt-516-monitor-interval-60s)

after:
'pcmk_status_timeout 61s'
[root@virt-516 ~]# pcs stonith config fence-virt-516 
 Resource: fence-virt-516 (class=stonith type=fence_xvm)
  Attributes: delay=5 pcmk_host_check=static-list pcmk_host_list=virt-516 pcmk_host_map=virt-516:virt-516.cluster-qe.lab.eng.brq.redhat.com pcmk_status_timeout=61s
  Operations: monitor interval=60s (fence-virt-516-monitor-interval-60s)

> OK


Marking as VERIFIED for pcs-0.11.1-10.el9

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 (new packages: pcs), 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-2022:2290