Bug 1391038

Summary:	consider server quorum while moving the host to maintenance.
Product:	[oVirt] ovirt-engine	Reporter:	RamaKasturi <knarra>
Component:	BLL.Gluster	Assignee:	Kaustav Majumder <kmajumde>
Status:	CLOSED WONTFIX	QA Contact:	SATHEESARAN <sasundar>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	4.1.0	CC:	bugs, godas, kmajumde, sabose
Target Milestone:	---	Flags:	sabose: needinfo? (kmajumde) sasundar: needinfo? (kmajumde) pm-rhel: ovirt-4.4? rule-engine: planning_ack? rule-engine: devel_ack? rule-engine: 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:	2020-08-25 10:58:10 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:

Description RamaKasturi 2016-11-02 13:03:20 UTC

Description of problem:
Server quorum should also be considered while moving the host to maintenance in ovirt.

Version-Release number of selected component (if applicable):
ovirt-engine-4.1.0-0.0.master.20161024211322.gitfc0de31.el7.centos.noarch

How reproducible:


Steps to Reproduce:
1. Have three hosts in virt+gluster cluster
2. stop glusterd on one of the node by running the command "service glusterd stop"
3. Now go to UI and move one of the node to maintenance by selecting 'stop glusterd service on the node'

Actual results:
Node will be moved to maintenance and server quorum will be lost because out of three nodes two of them are disconnected.

Expected results:
consider server quorum while moving the node to maintenance.

Additional info:

Comment 1 Sandro Bonazzola 2019-01-28 09:34:36 UTC

This bug has not been marked as blocker for oVirt 4.3.0.
Since we are releasing it tomorrow, January 29th, this bug has been re-targeted to 4.3.1.

Comment 2 Kaustav Majumder 2019-08-19 11:39:25 UTC

I have tried the steps above but it cannot be seen in the latest master of ovirt-engine

Screenshot of error shown:https://i.imgur.com/puxzHJ4.png

can we close this?

Comment 3 Sahina Bose 2019-08-19 12:10:39 UTC

I think  Bug 1741102 is another form of this? - so relevant to check server quorum if gluster services are stopped?

Comment 4 SATHEESARAN 2020-08-12 12:09:25 UTC

(In reply to Kaustav Majumder from comment #2)
> I have tried the steps above but it cannot be seen in the latest master of
> ovirt-engine
> 
> Screenshot of error shown:https://i.imgur.com/puxzHJ4.png
> 
> can we close this?

Hi Kaustav,

I tried the steps with ovirt-4.4.1

1. Stop glusterd directly from CLI on one of the HC node
2. Go to RHV manager UI ( Admin Portal ) and try to move one host to maintenance, selecting the checkbox 'Stop Gluster Service'

The node moves to maintenance, killing the bricks, leading to HE VM, and other VMs paused

Comment 5 Gobinda Das 2020-08-25 10:58:10 UTC

This case only reproducible only when user killing bricks from backend. If node is down from RHVM then UI does not allow user to move active host to maintenance.
Severity is very low for this, so closing this bug as no customer also faced such situation.