Bug 1311235

Summary:	backup-volfile-servers queried on every remount of gluster storage domain
Product:	[oVirt] vdsm	Reporter:	Sahina Bose <sabose>
Component:	Gluster	Assignee:	sankarshan <sankarshan>
Status:	CLOSED DUPLICATE	QA Contact:	SATHEESARAN <sasundar>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	4.17.18	CC:	amureini, bugs
Target Milestone:	ovirt-4.0.0-alpha	Flags:	amureini: ovirt-4.0.0? 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-02-24 08:08:35 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Storage	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1258386

Description Sahina Bose 2016-02-23 16:47:34 UTC

Description of problem:
When gluster volume is used as storage domain and mount path given as server1:/vol1, the volfile is fetched from server1 to introspect the possible  alternative servers (say, server2, server3). These servers are then passed as mount option "backup-volfile-servers=server2:server3".

However since the backup-volfile-servers option is not persisted, each time vdsm tries to mount the storage domain, the primary server (server1) is queried and activation of storage domain fails if primary server is down - even though the other servers in cluster are available.


The alternative backup servers should be persisted in engine database the first time, and used in subsequent mount calls

Comment 1 Allon Mureinik 2016-02-24 08:08:35 UTC

Seems like another bugzilla double-submit bug.

*** This bug has been marked as a duplicate of bug 1311234 ***