Bug 1455164

Summary:	[HE] - VDSM: add to a domain a special metadata that will not allow to put it to maintenance (to be used for hosted-engine domain)
Product:	[oVirt] vdsm	Reporter:	Yaniv Kaul <ykaul>
Component:	Core	Assignee:	Nir Soffer <nsoffer>
Status:	CLOSED DUPLICATE	QA Contact:	Raz Tamir <ratamir>
Severity:	high	Docs Contact:
Priority:	high
Version:	4.20.0	CC:	bugs, dchaplyg, ykaul, ylavi
Target Milestone:	ovirt-4.2.0	Keywords:	Improvement
Target Release:	---	Flags:	rule-engine: ovirt-4.2+
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:
Clones:	1455166 (view as bug list)		Environment:
Last Closed:	2017-09-04 08:53:43 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:	1455166

Description Yaniv Kaul 2017-05-24 12:07:05 UTC

Description of problem:
This is the VDSM side of the bug - the domain should include in its metadata a flag that will tell VDSM to refuse to put this domain into maintenance.
A separate bug will be for Engine to recognize this flag as well.

Comment 1 Yaniv Lavi 2017-06-11 15:05:33 UTC

Is this part of the storage stabilization effort?

Comment 2 Yaniv Kaul 2017-06-11 18:03:46 UTC

(In reply to Yaniv Lavi from comment #1)
> Is this part of the storage stabilization effort?

Yes.

Comment 3 Nir Soffer 2017-06-22 13:59:25 UTC

One issue, who will be responsible for putting the domain in maintenance when this
is actually needed?

For example, you cannot upgrade sanlock if there is an active storage domain.

Comment 4 Denis Chaplygin 2017-09-04 08:53:24 UTC

Hosted engine knows how to unmount it's domain and it can be done with 'hosted-engine --disconnect-storage' call.

We don't need metadata, as everything can be done on the engine side.

Comment 5 Denis Chaplygin 2017-09-04 08:53:43 UTC


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