Bug 2117599

Summary: [WebUI] Allow to start/stop of entire cluster
Product: Red Hat Enterprise Linux 9 Reporter: Ivan Devat <idevat>
Component: pcsAssignee: Ivan Devat <idevat>
Status: CLOSED ERRATA QA Contact: cluster-qe <cluster-qe>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 9.1CC: cluster-maint, idevat, mlisik, mmazoure, mpospisi, omular, svalasti, tojeline
Target Milestone: rcKeywords: Triaged
Target Release: 9.2Flags: pm-rhel: mirror+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: pcs-0.11.3-5.el9 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-05-09 07:18:34 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

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