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

Bug 1242955

Summary:	quota, snapd daemon is not running in test cluster framework
Product:	[Community] GlusterFS	Reporter:	Gaurav Kumar Garg <ggarg>
Component:	core	Assignee:	bugs <bugs>
Status:	CLOSED WORKSFORME	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	atumball, bugs, smohan
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-6.x	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-05-11 00:41:37 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:

Description Gaurav Kumar Garg 2015-07-14 13:22:30 UTC

Description of problem:

Quota daemon is not running in cluster test framework where multiple glusterd running on multiple ip address.

and for snapd daemon its running only on one node in cluster test framework.

Version-Release number of selected component (if applicable):

mainline

How reproducible:
always

Steps to Reproduce:
1. write test case with cluster framework where multiple glusterd running on multiple ip address.
2. enable quota, uss on the volume.
3.

Actual results:

quota daemon will not run on any node.
snapd daemon will run only on one node.

Expected results:
All the daemon in cluster framework should work normally.

Comment 1 Anand Avati 2015-07-14 13:38:48 UTC

REVIEW: http://review.gluster.org/11666 (glusterd: quotad, snapd daemon should run on the cluster framework.) posted (#1) for review on master by Gaurav Kumar Garg (ggarg)

Comment 2 Anand Avati 2015-08-20 13:16:46 UTC

REVIEW: http://review.gluster.org/11666 (glusterd: quotad, snapd daemon should run on the cluster framework.) posted (#2) for review on master by Gaurav Kumar Garg (ggarg)

Comment 3 Mike McCune 2016-03-28 22:39:30 UTC

This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions