Bug 1286565

Summary:	Warn about non-replica 3 gluster volume instead of failing connection to server
Product:	[oVirt] ovirt-engine	Reporter:	Ala Hino <ahino>
Component:	Frontend.WebAdmin	Assignee:	Ala Hino <ahino>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Aharon Canan <acanan>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	3.6.1	CC:	acanan, amureini, bugs, matt.deboer, nsoffer, sbonazzo, tnisan
Target Milestone:	ovirt-3.6.2	Flags:	rule-engine: ovirt-3.6.z+ ylavi: planning_ack+ tnisan: devel_ack+ rule-engine: testing_ack+
Target Release:	3.6.2
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-02-18 11:00:27 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:	1291705

Description Ala Hino 2015-11-30 09:17:11 UTC

Description of problem:
In oVirt 3.5, admins were able to create gluster sds with any volume type. However, in 3.6 and because we recommend using replica 3 volumes, we enforced using only replica 3 volumes. Enforcing means not allowing admins to create non-replica 3 volumes (although admins were still able to configure supported replicas). 
This enforcement introduced major issue when upgrading deployments using non-replica 3 volumes. Actually, 3.5 deployments using non-replica 3 volumes stopped working when upgraded to 3.6.

We would like to have the following behavior:
1. Allow creating sds with any replica count
2. If replica count is not 3, display an alert to the admin

Comment 1 Allon Mureinik 2015-12-02 10:36:35 UTC

*** Bug 1287211 has been marked as a duplicate of this bug. ***

Comment 2 Nir Soffer 2015-12-08 20:49:44 UTC

We should warn also when connecting to existing gluster storage domain, not only when creating a new gluster storage domain.

Comment 3 Ala Hino 2015-12-15 13:30:16 UTC

The work related to alerts will be tracked in following bug:

https://bugzilla.redhat.com/1291705

Comment 4 Ala Hino 2015-12-17 16:40:55 UTC

Please note doc-text for this bug is provided here: https://bugzilla.redhat.com/1123052

Comment 5 Sandro Bonazzola 2015-12-23 13:40:22 UTC

oVirt 3.6.2 RC1 has been released for testing, moving to ON_QA

Comment 6 Ala Hino 2016-01-05 16:20:20 UTC

For clarification:
Please note that log message is presented only when replica count is not supported as defined in "allowed_replica_counts" config value. By default, replica 1 and 3 are supported.
In addition, the log message appears in vdsm log. Look for:
"Unsupported replica count" 
or
"please upgrade volume to replica 3"

Comment 7 Ala Hino 2016-01-05 16:23:40 UTC

(In reply to Ala Hino from comment #6)
> For clarification:
> Please note that log message is presented only when replica count is not
> supported as defined in "allowed_replica_counts" config value. By default,
> replica 1 and 3 are supported.
> In addition, the log message appears in vdsm log. Look for:
> "Unsupported replica count" 
> or
> "please upgrade volume to replica 3"

Displaying an alert to the admin is not in the scope if this bug, see bug 1291705

Comment 8 Aharon Canan 2016-01-05 16:27:56 UTC

Verified 

vdsm-4.17.15-0.el7ev.noarch
rhevm-3.6.2-0.1.el6.noarch

from vdsm.log
=============
jsonrpc.Executor/4::WARNING::2016-01-05 18:23:25,517::storageServer::350::Storage.StorageServer.MountConnection::(validate) Unsupported replica count (2) for volume u'acanan_replica5', please upgrade volume to replica 3