Bug 1306588

Summary:	Fails to sync gluster bricks that use hostname not used by engine to identify host
Product:	[oVirt] ovirt-engine	Reporter:	Sahina Bose <sabose>
Component:	BLL.Gluster	Assignee:	Sahina Bose <sabose>
Status:	CLOSED DEFERRED	QA Contact:	SATHEESARAN <sasundar>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	3.6.0	CC:	bugs
Target Milestone:	---	Flags:	rule-engine: planning_ack? rule-engine: devel_ack? rule-engine: testing_ack?
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-03-31 09:52:49 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:
Bug Depends On:
Bug Blocks:	1258386

Description Sahina Bose 2016-02-11 11:45:31 UTC

Description of problem:

When a host has multiple interfaces and multiple FQDNs, and 
- gluster is peer probed with fqdn1 and bricks use fqdn2
- oVirt adds host with fqdn1(is only aware of fqdn1)
- gluster network attached to interface with fqdn2

bricks fail to sync correctly as it cannot identify fqdn2 as the one used by gluster network

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


How reproducible:
Always

Steps to Reproduce:
As above

Comment 1 Sahina Bose 2016-03-31 09:52:49 UTC

Recommended to use IP addresses to identify gluster bricks when setting up cluster in multiple network scenario - we do not plan to support the multiple FQDN in the immediate future