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

Bug 1434444

Summary:	ovirt throws a wrong error message when one node is already in maintenance and if user tries to move another node to maintenance with out stopping glusterd services
Product:	[oVirt] ovirt-engine	Reporter:	RamaKasturi <knarra>
Component:	Frontend.WebAdmin	Assignee:	Sahina Bose <sabose>
Status:	CLOSED NOTABUG	QA Contact:	RamaKasturi <knarra>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	4.1.1.2	CC:	bugs, knarra, sabose, sasundar
Target Milestone:	ovirt-4.1.5	Flags:	sasundar: ovirt-4.1? sasundar: planning_ack? sasundar: devel_ack? sasundar: testing_ack?
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-07-26 07:34:25 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:
Bug Blocks:	1411323

Description RamaKasturi 2017-03-21 14:06:00 UTC

Description of problem:
ovirt throws an error "cannot move host to maintenance since gluster quorum will be lost" when one of the node is in maintenance with glusterd services stopped and user tries to move another node to maintenance with out stopping glusterd services.

Version-Release number of selected component (if applicable):
Red Hat Virtualization Manager Version: 4.1.1.2-0.1.el7

How reproducible:
Always

Steps to Reproduce:
1. Install HC stack
2. Move one of the node to maintenance by stopping glusterd services
3. Now try moving another node to maintenance with out stopping glusterd services.

Actual results:
user will not be able to move the node to maintenance as ovirt throws an error " cannot move host to maintenance, gluster quourm will be lost for volumes <volnames>" 

Expected results:
Other node where glusterd services are not stopped should be moved to maintenance since gluster quourm will not be lost even if the node is moved to maintenance.

Additional info:

Comment 1 Sahina Bose 2017-05-30 07:30:02 UTC

I think there's a force option to ignore these checks. Could you retry using that?

Comment 2 RamaKasturi 2017-05-30 12:10:56 UTC

Re-tried by checking 'Ignore self-heal and quorum checks' and i see that able to move the host to maintenance mode where glusterd services are not stopped.