Bug 1860764 - Ensure that meaningful messages are logged, when edit cluster properties change and gluster service enabled
Summary: Ensure that meaningful messages are logged, when edit cluster properties chan...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: rhhi
Version: rhhiv-1.8
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
: RHHI-V 1.8.z Batch Update 1
Assignee: Ritesh Chikatwar
QA Contact: SATHEESARAN
URL:
Whiteboard:
Depends On: 1860769
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-07-27 05:18 UTC by Ritesh Chikatwar
Modified: 2020-10-09 14:56 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
: 1860769 (view as bug list)
Environment:
Last Closed: 2020-10-09 14:56:54 UTC
Embargoed:

Attachments (Terms of Use)

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
Note You need to log in before you can comment on or make changes to this bug.