Bug 1027213 - [RHSC] - Volumes from rhs console disappears and appears.
Summary: [RHSC] - Volumes from rhs console disappears and appears.
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: rhsc
Version: 2.1
Hardware: Unspecified
OS: Unspecified
medium
high
Target Milestone: ---
: RHGS 2.1.2
Assignee: Ramesh N
QA Contact: RamaKasturi
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-11-06 11:24 UTC by RamaKasturi
Modified: 2015-05-13 16:27 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-11-20 11:49:07 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description RamaKasturi 2013-11-06 11:24:19 UTC 
Description of problem:
Volumes from rhs console disappears and appears.

Version-Release number of selected component (if applicable):
rhsc-2.1.2-0.22.master.el6_4.noarch

How reproducible:


Steps to Reproduce:
1. Create a distribute volume and distribute volume and start it.
2. Now go to one of the node and stop glusterd.
3. Now start rebalance on the distribute volume.
4. Now check for the status by clicking on the status button in the drop down.
5. Now bring back the glusterd up.

Actual results:
It deletes all the volumes from console and gives event message saying "	
2013-Nov-06, 22:12
	
Detected deletion of volume vol_dis on cluster Cluster_AsyncTasks, and deleted it from engine DB.
	
2013-Nov-06, 22:12
	
Detected deletion of volume vol_dis_rep on cluster Cluster_AsyncTasks, and deleted it from engine DB."

After a while it adds all the volumes to the console, with all the bricks down in the volume.

Expected results:
It should not delete any volumes or any other resoruces from the console.

Additional info:
Comment 2 RamaKasturi 2013-11-06 11:34:06 UTC 
Attaching the sos reports :

http://rhsqe-repo.lab.eng.blr.redhat.com/sosreports/rhsc/1027213/
Comment 3 Ramesh N 2013-11-13 14:53:12 UTC 
Its difficult to find out which file (vdsm.log) related to which host in 
Gluster. Also please tell in which host glusterd was brought down.

From engine log, its clear that for some time the node 10.70.37.95 in the Gluster returns empty list for GlusterVolumeListVDSCommand.
Comment 4 RamaKasturi 2013-11-20 11:49:07 UTC 
I am not able to reproduce this issue in cb8 build. So closing it as not a bug.

Will reopen the bug, if it happens to see this bug.
Note You need to log in before you can comment on or make changes to this bug.