Created attachment 1954491 [details]
RHEL 9.0 browser console errors

Description of problem:
When fencing levels are configured, the web interface will not load cluster status. It is not possible to see cluster state or change its configuration.


Version-Release number of selected component (if applicable):
0.11.1-10.el9
0.11.4-6.el9_2

How reproducible:
always

Steps to Reproduce:
## Create a single node cluster
[root@r09-00-a ~]# pcs host auth r09-00-a.vm -u hacluster
Password: 
r09-00-a.vm: Authorized

[root@r09-00-a ~]# pcs cluster setup wui-fence-lvl r09-00-a.vm
No addresses specified for host 'r09-00-a.vm', using 'r09-00-a.vm'
Destroying cluster on hosts: 'r09-00-a.vm'...
r09-00-a.vm: Successfully destroyed cluster
Requesting remove 'pcsd settings' from 'r09-00-a.vm'
r09-00-a.vm: successful removal of the file 'pcsd settings'
Sending 'corosync authkey', 'pacemaker authkey' to 'r09-00-a.vm'
r09-00-a.vm: successful distribution of the file 'corosync authkey'
r09-00-a.vm: successful distribution of the file 'pacemaker authkey'
Sending 'corosync.conf' to 'r09-00-a.vm'
r09-00-a.vm: successful distribution of the file 'corosync.conf'
Cluster has been successfully set up.

[root@r09-00-a ~]# pcs cluster start --wait
Starting Cluster...
Waiting for node(s) to start...
Started

## Create 2 fence devices and set up fencing levels
[root@r09-00-a ~]# pcs stonith create fence-1 fence_xvm

[root@r09-00-a ~]# pcs stonith create fence-2 fence_xvm

[root@r09-00-a ~]# pcs stonith level add 1 r09-00-a.vm fence-1

[root@r09-00-a ~]# pcs stonith level add 2 r09-00-a.vm fence-2

Actual results:
When you open the web interface, after a short while, there will be a notification that says: "Communication error while: sync status of cluster "wui-fence-lvl". Details in the browser console." See the attachment for browser console output (see 9.0 logs for this reproducer, 9.2 logs have a different, more complex configuration).

Expected results:
No communication errors are shown, the web interface allows to see cluster status and modify its settings.

Additional info:
On RHEL 9.0, the cluster status is somehow loaded and shown despite the error. On RHEL 9.2, a loading animation is shown while loading cluster status that never goes away because of the communication error, even when browsing cluster detail. See the attached screenshot.