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

Bug 1105513

Summary:	Issue / strange behavior with GlusterFS nodes
Product:	[Retired] oVirt	Reporter:	Rene Koch <rkoch>
Component:	ovirt-engine-webadmin	Assignee:	Sahina Bose <sabose>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Pavel Stehlik <pstehlik>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	3.4	CC:	bazulay, bugs, ecohen, gklein, iheim, mgoldboi, ogofen, rbalakri, sabose, yeylon
Target Milestone:	---
Target Release:	3.5.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	gluster
Fixed In Version:	ovirt-engine-3.5.0_beta	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-10-17 12:37:08 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:	1116585
Bug Blocks:

Description Rene Koch 2014-06-06 09:50:31 UTC

Description of problem:
One of the glusterfs hosts, isn't able to mount one of the storage domains attached to the oVirt data center and therefor the status of this host changes every 5 minutes. The real issue here is, that the glusterfs hosts shouldn't mount the storage domains as they are in a cluster with virtualization disabled.

These are the messages which appear in oVirt webadmin:
2014-Jun-04, 13:30 State was set to Up for host gluster02-rz08.
2014-Jun-04, 13:26 Detected change in status of brick x.x.x.x:/export/brick01/vol01 of volume vol01 from DOWN to UP.
2014-Jun-04, 13:25 Host xxx cannot access one of the Storage Domains attached to the Data Center Default. Setting Host state to Non-Operational.

Version-Release number of selected component (if applicable):
oVirt 3.4.1 with CentOS 6.5 (latest updates)

How reproducible:
If you create a datacenter with 2 clusters (1 virtualization only and 1 gluster only) all the gluster cluster hosts will try to mount the storage domains.

Steps to Reproduce:
1. Create a new datacenter (or use default one)
2. Create 2 cluster (1 virtualization only, 1 gluster only)
3. Add hosts to gluster cluster

Actual results:
All storage hosts in the gluster cluster try to mount the storage domains of the datacenter. This works fine during installation but in our setup it failed when rebooting 1 host. But the issue for me is not that it fails because the volume is fine, it's the reason that the storage nodes do mount the storage domains.

Expected results:
The properties of a cluster should be checked whether if the hosts are responsible for virtualization or not and if not, the storage domains of the datacenter shouldn't be mounted.

Additional info:

Comment 1 Sahina Bose 2014-08-13 11:07:35 UTC

Moving it to Assigned, as still see the issue - 	
2014-Aug-13, 04:30
Host 10.70.x.x cannot access the Storage Domain(s) <UNKNOWN> attached to the Data Center DC34. Setting Host state to Non-Operational.

Comment 2 Sandro Bonazzola 2014-10-17 12:37:08 UTC

oVirt 3.5 has been released and should include the fix for this issue.