Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Description of problem:
The new web UI doesn't allow to stop cluster nodes if '--force' is required. This usually happens when stopping the node would cause loss of the quorum. As a consequence, it is not possible to stop all cluster nodes using the new web UI, as that always results in losing the quorum.
Version-Release number of selected component (if applicable):
pcs-0.11.2-1.el9
How reproducible:
always, easily
Steps to Reproduce:
1. Run a cluster in such state that stopping one node would cause loss of the quorum. The easiest is to run a one-node cluster.
2. Log in to web UI and try stopping a running node of the cluster.
Actual results:
Task: stop node rh90-node1" failed
Error: Stopping the node will cause a loss of the quorum, use --force to override
Details in the browser console.
Expected results:
Display a dialog with the received error message: "Stopping the node will cause a loss of the quorum". Ask the user if they want to proceed. If confirmed, stop the cluster node.
DevTestResults:
1. Clicking on “Stop” in the node detail of the only node from a single-node cluster.
2. “Stop Node?” modal window is displayed. Clicking on “Stop”.
3. “Node stop failed” modal window is displayed. Modal text: “Task: stop node "r09-02-a.vm" failed: Error: Stopping the node will cause a loss of the quorum . Details in the browser console. The error can be overridden.” Clicking on “Proceed anyway”.
4. “Node successfully stopped” modal window is displayed.
[root@virt-023 ~]# 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.
After moving to the "Nodes" tab and clicking the "Stop" button, a modal window is displayed to the user. Then, after confirming that the user actually wants to stop the node, the user is notified that the stopping node task failed and that stopping the node will cause the loss of quorum.
In this case, the user has the option to cancel node stop or "proceed anyway".
If the user chooses to "proceed anyway", the node is successfully stopped.
> Marking as VERIFIED SanityOnly for pcs-0.11.4-4.el9
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