Created attachment 753605[details]
Screenshot of RHEVM UI, showing warning statement while removing bricks
Description of problem:
While removing bricks from a volume, the warning message has repetitive statements.
(i.e)"Are you sure you want to remove the following Are you sure want to remove the following Brick(s)??"
Version-Release number of selected component (if applicable):
RHEVM 3.2 [3.2.0-10.26.rc.el6ev]
How reproducible:
Always
Steps to Reproduce:
1. Try to remove a brick from a volume and look for the warning message
2.
3.
Actual results:
"Are you sure you want to remove the following Are you sure want to remove the following Brick(s)??"
Expected results:
"Are you sure want to remove the following Brick(s)??"
Additional info:
Attached the screenshot of the error
Verified this bug with RHEVM 3.3.0-0.34.beta1.el6ev and glusterfs-3.4.0.44rhs-1
Steps to Verify
===============
1. In a 3.2 compatibility Data Center created a 3.2 compatible gluster-enabled
cluster
2. Add 2 RHS Nodes to this cluster
3. Using RHEVM UI, Create a distributed-replicate volume with 4 bricks, (2X2)
4. Started the volume using RHEVM UI
5. Tried removing the brick and there was a warning message as expected in correct way(i.e) error messages are present only once not repetitive
Moving this bug as VERIFIED
Created attachment 753605 [details] Screenshot of RHEVM UI, showing warning statement while removing bricks Description of problem: While removing bricks from a volume, the warning message has repetitive statements. (i.e)"Are you sure you want to remove the following Are you sure want to remove the following Brick(s)??" Version-Release number of selected component (if applicable): RHEVM 3.2 [3.2.0-10.26.rc.el6ev] How reproducible: Always Steps to Reproduce: 1. Try to remove a brick from a volume and look for the warning message 2. 3. Actual results: "Are you sure you want to remove the following Are you sure want to remove the following Brick(s)??" Expected results: "Are you sure want to remove the following Brick(s)??" Additional info: Attached the screenshot of the error