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.
Bug 2182810 - [WebUI] fence levels prevent loading of cluster status
Summary: [WebUI] fence levels prevent loading of cluster status
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: pcs
Version: 9.0
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: rc
: 9.3
Assignee: Ivan Devat
QA Contact: cluster-qe
Steven J. Levine
URL:
Whiteboard:
Depends On:
Blocks: 2183180 2183191 2183192
TreeView+ depends on / blocked
 
Reported: 2023-03-29 17:28 UTC by Michal Pospisil
Modified: 2023-11-07 09:04 UTC (History)
10 users (show)

Fixed In Version: pcs-0.11.5-1.el9
Doc Type: Bug Fix
Doc Text:
.`pcsd` Web UI now displays cluster status when fence levels are configured Previously, the `pcsd` Web UI did not display cluster status when fence levels were configured. With this fix, you can now view the cluster status and change the cluster settings with the Web UI when fence levels are configured.
Clone Of:
: 2183180 2183191 2183192 (view as bug list)
Environment:
Last Closed: 2023-11-07 08:23:11 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
RHEL 9.0 browser console errors (34.79 KB, text/plain)
2023-03-29 17:28 UTC, Michal Pospisil 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker CLUSTERQE-6646 0 None None None 2023-04-19 22:20:48 UTC
Red Hat Issue Tracker RHELPLAN-153440 0 None None None 2023-03-29 17:29:39 UTC
Red Hat Product Errata RHSA-2023:6316 0 None None None 2023-11-07 08:24:42 UTC

Description Michal Pospisil 2023-03-29 17:28:05 UTC 
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.
Comment 7 Ivan Devat 2023-03-30 16:21:34 UTC 
https://github.com/ClusterLabs/pcs-web-ui/commit/e350ccc9e09efe1750cb2d6a29673026138bdabd
Comment 10 Michal Pospisil 2023-05-26 09:29:02 UTC 
DevTestResults:

[root@r09-03-a ~]# rpm -q pcs
pcs-0.11.5-1.el9.x86_64

The web interface is working with fencing levels configured.
Comment 15 Ivan Devat 2023-06-28 05:51:00 UTC 
Steven, yes - this is perfectly ok for a user.
Comment 20 Ivan Devat 2023-08-11 08:02:48 UTC 
Steven: I think you express it very well and kept the message technically correct, thanks.
Comment 22 errata-xmlrpc 2023-11-07 08:23:11 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 (Low: pcs security, 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/RHSA-2023:6316
Note You need to log in before you can comment on or make changes to this bug.