Bug 1445753

Summary:	The engine blocks deactivation of storage domain in Inactive (in problem) status
Product:	[oVirt] ovirt-engine	Reporter:	Liron Aravot <laravot>
Component:	Backend.Core	Assignee:	Allon Mureinik <amureini>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Natalie Gavrielov <ngavrilo>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	4.1.1	CC:	amureini, bugs, tnisan
Target Milestone:	ovirt-4.2.0	Flags:	rule-engine: ovirt-4.2+
Target Release:	4.2.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:	undefined	Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-12-20 11:11:16 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:

Description Liron Aravot 2017-04-26 12:47:17 UTC

Description of problem:
The PreparingForMaintenance status was added in order to make sure
that when a domain moves to Maintenance status it's not accessed by any host
in the data center.

Currently we don't allow to deactivate a domain when it's status is Inactive, while on that status it may be still accessed by some of the DC hosts.


How reproducible:
Always

Steps to Reproduce:
1. Have a DC with two hosts and two domains, each on a different storage server.
2. Block the connection between the two hosts and the non master domain.
3. Wait for the domain to become Inactive (the default time interval for that is 5 minutes).
4. Attempt to deactivate the domain.

Actual results:
The engine blocks the deactivation of the domain.

Expected results:
The engine shouldn't allow to deactivat the domain.


Additional info:

Comment 1 Natalie Gavrielov 2017-08-06 13:43:11 UTC

(In reply to Liron Aravot from comment #0)
> Actual results:
> The engine blocks the deactivation of the domain.
> 
> Expected results:
> The engine shouldn't allow to deactivat the domain.

I think the actual and expected result here are pretty much the same.
Can you please clarify this for me (I don't want to make assumptions that might be wrong)

Thanks

Comment 2 Allon Mureinik 2017-08-06 16:02:26 UTC

(In reply to Natalie Gavrielov from comment #1)
> (In reply to Liron Aravot from comment #0)
> > Actual results:
> > The engine blocks the deactivation of the domain.
> > 
> > Expected results:
> > The engine shouldn't allow to deactivat the domain.
> 
> I think the actual and expected result here are pretty much the same.
> Can you please clarify this for me (I don't want to make assumptions that
> might be wrong)
> 
> Thanks

Yes, this is clearly not the intention of the BZ.

Actual results:
Engine blocks the deactivation of an Inactive domain. Probably something like "Cannot deactivate Storage Domain. The relevant Storage Domain's status is Inactive".

Expected results:
Engine should NOT block the deactivation of an Inactive domain. I.e., clicking the button (or sending a REST request) should not fail, and the domain should (after a short period) move to MAINTENANCE.

Comment 3 Natalie Gavrielov 2017-08-07 11:55:24 UTC

Verified using builds:
ovirt-engine-4.2.0-0.0.master.20170725202023.git561151b.el7.centos.noarch
vdsm-4.20.1-218.git1b7671f.el7.centos.x86_64

Comment 4 Sandro Bonazzola 2017-12-20 11:11:16 UTC

This bugzilla is included in oVirt 4.2.0 release, published on Dec 20th 2017.

Since the problem described in this bug report should be
resolved in oVirt 4.2.0 release, published on Dec 20th 2017, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.