Bug 916104 - 'gluster peer detach force' executed from gluster CLI not being reflected on the UI
Summary: 'gluster peer detach force' executed from gluster CLI not being reflected on ...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine-webadmin-portal
Version: 3.2.0
Hardware: All
OS: All
high
medium
Target Milestone: ---
: 3.3.0
Assignee: Sahina Bose
QA Contact: SATHEESARAN
URL:
Whiteboard: gluster
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-02-27 10:11 UTC by Shruti Sampat
Modified: 2016-02-10 18:58 UTC (History)
15 users (show)

Fixed In Version: is9
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-01-21 22:18:55 UTC
oVirt Team: Gluster
Target Upstream Version:
Embargoed:
scohen: Triaged+


Attachments (Terms of Use)
engine logs (3.17 MB, text/x-log)
2013-02-27 10:13 UTC, Shruti Sampat
no flags Details
vdsm logs from server 1 (10.95 MB, text/x-log)
2013-02-27 10:15 UTC, Shruti Sampat
no flags Details
vdsm logs from server 2 (13.88 MB, text/x-log)
2013-02-27 10:18 UTC, Shruti Sampat
no flags Details
gluster logs from server 1 (15.74 MB, text/x-log)
2013-02-27 10:21 UTC, Shruti Sampat
no flags Details
gluster logs from server 2 (3.86 MB, text/x-log)
2013-02-27 10:23 UTC, Shruti Sampat
no flags Details

Description Shruti Sampat 2013-02-27 10:11:27 UTC
Description of problem:
---------------------------------------
When executing 'gluster peer detach force' of a server in the cluster, the command is successful at the CLI, but the UI fails to sync with the CLI. The detached server continues to show up in the UI.

Version-Release number of selected component (if applicable):
Red Hat Enterprise Virtualization Manager Version: 3.2.0-8.el6ev 

How reproducible:
Frequently

Steps to Reproduce:
1. On one of the nodes in a two-node cluster, run the command 'gluster peer detach <IP-of-the-other-node> force'
  
Actual results:
The UI still shows the detached server.

Expected results:
The UI should be in sync with the CLI and thus remove the detached server.

Additional info:

Comment 1 Shruti Sampat 2013-02-27 10:13:17 UTC
Created attachment 703347 [details]
engine logs

Comment 2 Shruti Sampat 2013-02-27 10:15:40 UTC
Created attachment 703348 [details]
vdsm logs from server 1

Comment 3 Shruti Sampat 2013-02-27 10:18:17 UTC
Created attachment 703350 [details]
vdsm logs from server 2

Comment 4 Shruti Sampat 2013-02-27 10:21:24 UTC
Created attachment 703351 [details]
gluster logs from server 1

Comment 5 Shruti Sampat 2013-02-27 10:23:22 UTC
Created attachment 703352 [details]
gluster logs from server 2

Comment 6 Sahina Bose 2013-08-21 09:17:49 UTC
This bug has been fixed as part of changes that have gone into the Gluster sync job, so moving it to ON_QA

Comment 7 SATHEESARAN 2013-11-20 10:39:19 UTC
Verified with following steps, in 
Red Hat Enterprise Virtualization Manager Version: 3.3.0-0.34.beta1.el6ev 
[IS23.1]

1. Created a Datacenter with 3.2 compatibility
2. Created a cluster with 3.2 compatibility
3. Added 3 RHS Nodes using RHEVM UI
4. From gluster cli, did a force removal of a peer
(i.e) gluster peer remove <node3> force
5. Verified that the host was removed from RHEVM UI

Additional Tests Done,
1. Added a new host ( peer probe from gluster cli ) and verified it.
2. Did a normal detach without force and verified it
(i.e) gluster peer detach <node3>

So marking this bug as VERIFIED

Comment 8 Itamar Heim 2014-01-21 22:18:55 UTC
Closing - RHEV 3.3 Released

Comment 9 Itamar Heim 2014-01-21 22:25:10 UTC
Closing - RHEV 3.3 Released


Note You need to log in before you can comment on or make changes to this bug.