Bug 1043047

Summary:	[RFE] Storage domain gets activated even if one of the host can't access it
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Pratik Pravin Bandarkar <pbandark>
Component:	ovirt-engine	Assignee:	Nobody <nobody>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Raz Tamir <ratamir>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	3.2.0	CC:	dmoessne, klaas, lpeer, mlipchuk, psahoo, rbalakri, Rhev-m-bugs, scohen, srevivo, tnisan, ylavi
Target Milestone:	---	Keywords:	FutureFeature, Improvement
Target Release:	---	Flags:	sherold: Triaged+
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-06-04 08:31:49 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:

Description Pratik Pravin Bandarkar 2013-12-13 20:25:00 UTC

Description of problem:
Among all hosts if one host dont have connection with storage and if we try adding storage domain then, storage domain gets added successfully. Further another host which don't have connection with storage, move into non-operational state.

RHEV should check if all hosts in Data center have access to the storage domain, before adding the storage domain. If any of the host don't have access then, RHEV should throw some error message while adding storage it-self. For ex: "host <hostname> dont have access to the storage".

storage domain can be added, but activation of new storage domain should fail if one of the host fails to access it. Hypervisor should not go to Non-Operational while trying to activate a
new storage domain.

Version-Release number of selected component (if applicable):
RHEV3.2/3.2

How reproducible:
100%

Steps to Reproduce:
1. Add two hosts.
2. unmap any of the host from storage.
3. Try creating new storage domain.

Actual results:
Among all hosts if one host dont have connection with storage and if we try adding storage domain then, storage domain gets added successfully. Further another host which don't have connection with storage, move into non-operational state.

Expected results:
I think, In 3.2, storage domain can be added, but activation of new storage domain should fail if one of the host fails to access it. Hypervisor should not go to Non-Operational while trying to activate a
new storage domain.

Additional info:

Comment 4 Liron Aravot 2014-03-02 13:50:10 UTC

Allon, how do you want to handle it? possibly we can make it to be a 3.5 RFE, basically same issue as "prepare for maintenace" (here it will be "prepare for activation or something like that) if we do want to proceed with it.

Comment 5 Allon Mureinik 2014-03-11 10:03:39 UTC

(In reply to Liron Aravot from comment #4)
> Allon, how do you want to handle it? possibly we can make it to be a 3.5
> RFE, basically same issue as "prepare for maintenace" (here it will be
> "prepare for activation or something like that) if we do want to proceed
> with it.

We need to see how this fits in our 3.5 capacity, but definitely an RFE that should be tackled.

Comment 10 Klaas Demter 2017-11-15 08:59:31 UTC

could this bring down many hypervisors or even whole clusters if they can't access the storage domain? I only had the problem with one hypervisor like the the original reporter.

Comment 12 Klaas Demter 2018-05-04 06:46:16 UTC

This is fixed in 4.1, can be closed

Comment 13 Franta Kust 2019-05-16 13:03:28 UTC

BZ<2>Jira Resync