Bug 1860764

Summary: Ensure that meaningful messages are logged, when edit cluster properties change and gluster service enabled
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: Ritesh Chikatwar <rchikatw>
Component: rhhiAssignee: Ritesh Chikatwar <rchikatw>
Status: CLOSED CURRENTRELEASE QA Contact: SATHEESARAN <sasundar>
Severity: medium Docs Contact:
Priority: unspecified    
Version: rhhiv-1.8CC: godas, rhs-bugs
Target Milestone: ---Keywords: ZStream
Target Release: RHHI-V 1.8.z Batch Update 1   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of:
: 1860769 (view as bug list) Environment:
Last Closed: 2020-10-09 14:56:54 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1860769    
Bug Blocks:    

Description Ritesh Chikatwar 2020-07-27 05:18:39 UTC 
Description
-------------
When cluster compatiblity version change and try to submit,
cluster edit fails for error message - 
Error while executing action: CLUSTER_CANNOT_DISABLE_GLUSTER_WHEN_CLUSTER_CONTAINS_VOLUMES
This message can be more meaningful for users to understand

Version
-------
RHHI-V 1.8
RHVH 4.4
vdsm-4.40.13-1.el8ev.x86_64
glusterfs-6.0-32.el8rhgs.x86_64

How reproducible
-----------------
Always

Steps to reproduce
-------------------
1. Go to Cluster edit
2. Change the Compatibility Version
3. Click OK

Actual results
---------------
Cluster edit fails with not so meaning message

Expected results
-----------------
Cluster edit should fail with more meaningful error message
Comment 3 SATHEESARAN 2020-08-17 07:56:28 UTC 
This error doesn't occur now to verify the error message.
This is verified by Ritesh in the development environment, by introducing suitable errors and the
error messages is logged more clearly in this case.

Considering that as the only way to hit this issue now, the same method is considered for
verification of this bug

Verified with RHV 4.4.2