Bug 2117650

Summary: [Web-UI] It is not possible to enable SBD using web UI
Product: Red Hat Enterprise Linux 8 Reporter: Ivan Devat <idevat>
Component: pcsAssignee: Ivan Devat <idevat>
Status: CLOSED ERRATA QA Contact: cluster-qe <cluster-qe>
Severity: high Docs Contact:
Priority: high    
Version: 8.7CC: cluster-maint, idevat, kmalyjur, mlisik, mmazoure, mpospisi, nhostako, omular, tojeline
Target Milestone: rcKeywords: Regression, Triaged
Target Release: 8.7   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: pcs-0.10.14-4.el8 Doc Type: No Doc Update
Doc Text:
The affected packages have never been released.
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-11-08 09:14:01 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 14:05:06 UTC
Description of problem:
Error during SBD enable.


Steps to Reproduce:
1. In web ui, in cluster detail, in "FENCE DEVICES" tab, click on "SBD"
2. Click on "Enable SBD" in displayed dialog
3. Click on "Enable SBD" in the next displayed dialog 


Actual results:
Box with message "(Bad Request) Unable to enable sbd in cluster:" is displayed.


Expected results:
Box with message "SBD enabled! You have to restart cluster in order to apply changes." is displayed.

Comment 5 Miroslav Lisik 2022-08-18 11:56:37 UTC
DevTestResults:

[root@r8-node-01 ~]# rpm -q pcs
pcs-0.10.14-4.el8.x86_64

1. In web ui, in cluster detail, in "FENCE DEVICES" tab, click on "SBD"
2. Click on "Enable SBD" in displayed dialog
3. Click on "Enable SBD" in the next displayed dialog

Result:

Info dialog has been displayed: "SBD enabled! You have to restart cluster in
order to apply changes." Dialog is closed after click on "OK" button. You can
see in the SBD dialog, that SBD has been enabled.

Comment 11 errata-xmlrpc 2022-11-08 09:14:01 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 (Moderate: 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-2022:7447