Bug 1023289

Summary: [RHSC] When multiple hosts of the same cluster are selected for removal, show an appropriate error message.
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: Shruti Sampat <ssampat>
Component: rhscAssignee: Ramesh N <rnachimu>
Status: CLOSED DUPLICATE QA Contact: Shruti Sampat <ssampat>
Severity: medium Docs Contact:
Priority: low    
Version: 2.1CC: dtsang, kmayilsa, knarra, mmahoney, pprakash, rhs-bugs, sdharane
Target Milestone: ---Keywords: ZStream
Target Release: RHGS 2.1.2   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-11-20 11:01:17 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 Shruti Sampat 2013-10-25 06:19:50 UTC
Description of problem:
-----------------------
When the user tries to remove multiple hosts from a cluster at once, the action fails.

For e.g., when the user tries to remove host2, host3, and host4 from a cluster, the following message is seen - 

Error while executing action:

host3:

    Cannot remove Host. Related operation is currently in progress. Please try again later.

host4:

    Cannot remove Host. Related operation is currently in progress. Please try again later.

host2 is removed, but host3 and host4 are not. 

The error message shown should  better convey the reason for failure to remove host3 and host4.

Version-Release number of selected component (if applicable):
Red Hat Storage Console Version: 2.1.2-0.21.beta1.el6_4 

How reproducible:
Always

Steps to Reproduce:
1. Add 4 nodes to a cluster and move 3 of them to Maintenance.
2. Select the 3 nodes moved to Maintenance and click on Remove.

Actual results:
The above described error is seen.

Expected results:
Error message should better convey the reason for failure to remove multiple hosts from the same cluster.

Additional info:

Comment 2 Dusmant 2013-11-12 16:49:26 UTC
Only if time permits, we will try to fix this. Otherwise, we will drop it out of Corbett

Comment 3 Ramesh N 2013-11-20 11:01:17 UTC

*** This bug has been marked as a duplicate of bug 1024997 ***