Bug 1306588 - Fails to sync gluster bricks that use hostname not used by engine to identify host
Summary: Fails to sync gluster bricks that use hostname not used by engine to identify...
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Gluster
Version: 3.6.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: Sahina Bose
QA Contact: SATHEESARAN
URL:
Whiteboard:
Depends On:
Blocks: Gluster-HC-1
TreeView+ depends on / blocked
 
Reported: 2016-02-11 11:45 UTC by Sahina Bose
Modified: 2017-12-22 07:43 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-03-31 09:52:49 UTC
oVirt Team: Gluster
Embargoed:
rule-engine: planning_ack?
rule-engine: devel_ack?
rule-engine: testing_ack?

Attachments (Terms of Use)

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
Note You need to log in before you can comment on or make changes to this bug.