Bug 1054374

Summary: [RHSC][IE] - When moving a host to another cluster, the Edit host dialog waits for a long time and the image does not move in a circle.
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: RamaKasturi <knarra>
Component: rhscAssignee: Ramesh N <rnachimu>
Status: CLOSED EOL QA Contact: storage-qa-internal <storage-qa-internal>
Severity: low Docs Contact:
Priority: unspecified    
Version: 2.1CC: knarra, mmahoney, mmccune, nlevinki, rhs-bugs, ssampat
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-12-03 17:12:42 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:
Attachments:
Description Flags
Attaching the screenshot2 none

Description RamaKasturi 2014-01-16 17:25:26 UTC
Created attachment 851187 [details]
Attaching the screenshot2

Description of problem:
When moving a host to another cluster, the Edit host dialog waits for a long time
and the image does not move in a circle. 

Version-Release number of selected component (if applicable):
rhsc-2.1.2-0.32.el6rhs.noarch

How reproducible:
Always

Steps to Reproduce:
1.  Create 3.2 and 3.3 clusters and add a host to 3.3 cluster
2.  Move the host to maintenance.
3.  Now click on the edit button and select the 3.2 cluster.


Actual results:
The Edit host dialog waits for a long time and the image does not move in a circle. 

Expected results:
Edit host dialog should respond in a proper way and the image should move till operation completes.

Additional info:

Comment 2 Vivek Agarwal 2015-12-03 17:12:42 UTC
Thank you for submitting this issue for consideration in Red Hat Gluster Storage. The release for which you requested us to review, is now End of Life. Please See https://access.redhat.com/support/policy/updates/rhs/

If you can reproduce this bug against a currently maintained version of Red Hat Gluster Storage, please feel free to file a new report against the current release.