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 2117599 - [WebUI] Allow to start/stop of entire cluster
Summary: [WebUI] Allow to start/stop of entire cluster
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: pcs
Version: 9.1
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-08-11 12:36 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:34 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker CLUSTERQE-6222 0 None None None 2022-12-01 17:23:32 UTC
Red Hat Issue Tracker RHELPLAN-130943 0 None None None 2022-08-11 12:50:21 UTC
Red Hat Product Errata RHBA-2023:2151 0 None None None 2023-05-09 07:18:55 UTC

Description Ivan Devat 2022-08-11 12:36:10 UTC
Currently, only a particular cluster node can be started/stopped. It is needed to be able start/stop the entire cluster.

Comment 2 Miroslav Lisik 2022-10-26 13:06:34 UTC
DevTestResults:

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

1. Add a cluster into the web ui
2. In the Clusters dashbord click on cluster name
3. In the cluster detail there are 2 newly added buttons 'Start' and 'Stop'

Buttons works as expected. After confirming a dialog window the selected action is performed.

Comment 6 svalasti 2023-01-24 14:09:10 UTC
[root@virt-594 ~]# rpm -q pcs
pcs-0.11.4-4.el9.x86_64

Only a basic check for this implemented feature of stopping/starting the entire cluster has been performed. 
After selecting the desired 'cluster' from the list of available clusters, the entire cluster can be reliably started or stopped by using the available 'Start' and 'Stop' buttons.
This new feature works reliably even in the case of multiple cluster starts or stops.

Marking as VERIFIED SanityOnly for pcs-0.11.4-4.el9

Comment 8 errata-xmlrpc 2023-05-09 07:18:34 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.