Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1207150

Summary:	[New] - Host status does not move to non-operational when glusterd is down.
Product:	[Retired] oVirt	Reporter:	RamaKasturi <knarra>
Component:	ovirt-engine-webadmin	Assignee:	Darshan <dnarayan>
Status:	CLOSED CURRENTRELEASE	QA Contact:	RamaKasturi <knarra>
Severity:	high	Docs Contact:
Priority:	high
Version:	3.6	CC:	ahino, amureini, bugs, ecohen, gklein, knarra, lsurette, mgoldboi, mkovgan, rbalakri, sabose, yeylon, ylavi
Target Milestone:	---
Target Release:	3.5.3
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	gluster
Fixed In Version:	vdsm-4.16.16-1.el6ev	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-06-15 08:39:10 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Gluster	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1184376, 1184380, 1187461, 1203154

Description RamaKasturi 2015-03-30 10:23:40 UTC

Description of problem:
When glusterd is down on one of the node in the cluster host should go to non operational which is not happening as of now. Host status is always shown as UP even when glusterd is down on that node.

Version-Release number of selected component (if applicable):
ovirt-engine-webadmin-portal-3.6.0-0.0.master.20150329172249.git660d494.el6.noarch

How reproducible:
Always

Steps to Reproduce:
1. Add gluster nodes to ovirt
2. Now stop glusterd in one the node in the cluster.
3. 

Actual results:
Ovirt still shows the node with up status and node does not go to non-operational.

Expected results:
When glusterd is down on the node, host status in UI should show it as "non-operational".

Additional info:

Comment 1 Ala Hino 2015-03-31 08:51:45 UTC

Please note that glusterd is the management daemon and it's job is to look for other peers and distribute information across nodes. 
Once a client is connected to a gluster volume, it ends up talking directly to the brick processes - i.e glusterfsd processes. There is a glusterfsd process per volume.
If you want to simulate one of the gluster nodes being unreachable from gluster perspective, shut down glusterd and kill the glusterfsd processes.

Comment 2 Ramesh N 2015-04-02 10:18:54 UTC

This happens only in the case when JSON RPC is used for communication. Exception handling is different in JSON RPC and currently its not handled properly for gluster related exception. As result, always 'JsonRpcInternalError"(Code: -32603) is returned from VDSM for any exception.

Comment 3 Max Kovgan 2015-04-14 08:00:46 UTC

accidentally caught this with our script and moved it to "ON_QA"
reverting back to how it was.

Comment 4 RamaKasturi 2015-05-19 07:18:25 UTC

Verified and works fine with build ovirt-engine-3.6.0-0.0.master.20150517172245.git089e126.el6.noarch.

When host is added to ovirt in json/xml rpc mode and if glusterd is down on that node ovirt moves the node to non operational.

Comment 5 Sandro Bonazzola 2015-06-15 08:39:10 UTC

This is an automated message.
oVirt 3.5.3 has been released on June 15th 2015 and should include the fix for this BZ. Moving to closed current release.