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 2112079 - [WebUi] A stopped cluster is displayed confusingly
Summary: [WebUi] A stopped cluster is displayed confusingly
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: pcs
Version: 9.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: 9.2
Assignee: Ivan Devat
QA Contact: cluster-qe@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-07-28 18:43 UTC by Ivan Devat
Modified: 2023-05-09 07:39 UTC (History)
8 users (show)

Fixed In Version: pcs-0.11.3-5.el9
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-05-09 07:18:23 UTC
Type: Bug
Target Upstream Version:
Embargoed:
pm-rhel: mirror+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker CLUSTERQE-6218 0 None None None 2022-12-01 17:24:01 UTC
Red Hat Issue Tracker RHELPLAN-129518 0 None None None 2022-07-28 18:46:28 UTC
Red Hat Product Errata RHBA-2023:2151 0 None None None 2023-05-09 07:18:47 UTC

Description Ivan Devat 2022-07-28 18:43:09 UTC 
When a cluster is stopped (i.e. no node is online and at least one is offline) there are wrong information that no resource/fence device/constraint is configured. Also there is not aggregated information about this fact (a user can only deduce this information from state of particular nodes).

There should be explicit information that cluster is stopped and information about resources etc. is not available.
Comment 1 Ivan Devat 2022-07-29 09:32:20 UTC 
Also add a warning into tasks (e.g. resource create, fence device create, constraint create, ...) that will fail when cluster is stopped.
Comment 2 Ivan Devat 2022-10-19 08:21:29 UTC 
https://github.com/ClusterLabs/pcs-web-ui/commit/945c73e47169bcc600f0ac1eb8945c6c4a6e031b
Comment 3 Miroslav Lisik 2022-10-26 13:08:51 UTC 
DevTestResults:

[root@r92-1 ~]# rpm -q pcs
pcs-0.11.3-5.el9.x86_64

1. Setup a stopped cluster and add it to the web ui.
2. Check the clusters dashboard. There is a label 'offline' next to the cluster name.
3. Click on the cluster name and on the cluster page check the breadcrums menu. There is also label 'offline' next to the cluster name.
4. Switch to the Resources tab. There is information about stopped cluster and button 'Start Cluster' for the starting cluster.
5. Click on the 'Create Resource' button. A dialog windows is showed up and informs that resources cannot be created on stopped cluster.
6. Start cluster and wait for label next to the cluster name to change. Label changes to 'inoperative' and then after cluster gets quarate changes to 'running.
7. Stop one cluster node and check the label. Label is changed to 'degraded'.
Comment 8 svalasti 2023-01-25 12:43:27 UTC 
[root@virt-594 ~]# rpm -q pcs
pcs-0.11.4-4.el9.x86_64

Only a basic check of this implemented feature has been performed. Our priority at the moment is to automate the tasks that are possible by using the GUI.
When the entire cluster is stopped, this information is advertised to the user through a small icon next to the cluster name, which indicates that the cluster is currently "offline".
Similarly, in this case, when a user(s) click on the "Resources tab", they are notified that it is not possible to get resources from the stopped cluster, and they must first start the cluster to enable resource configuration.
If at least one node is stopped (not all cluster nodes), then the user is informed that the cluster is "degraded" (small icon next to the cluster name). 
In this case, the user is provided with information about resources and can configure resources/clones/groups (this is the correct and desired behavior).
If all nodes are started, the user is informed that the cluster is "running" (small icon next to the cluster name).
After this update, the user is no longer incorrectly informed that no resource/constraint/fence device is configured.

> Marking as VERIFIED SanityOnly for pcs-0.11.4-4.el9
Comment 10 errata-xmlrpc 2023-05-09 07:18:23 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 (pcs 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/RHBA-2023:2151
Note You need to log in before you can comment on or make changes to this bug.