Bug 593244 - Separating the inactive status for storage domain to inactive and maintenance
Summary: Separating the inactive status for storage domain to inactive and maintenance
Alias: None
Product: oVirt
Classification: Retired
Component: ovirt-engine-core (Show other bugs)
(Show other bugs)
Version: unspecified
Hardware: All Linux
Target Milestone: m1
: 3.1
Assignee: Jon Choate
QA Contact:
Whiteboard: storage
Keywords: FutureFeature
Depends On:
TreeView+ depends on / blocked
Reported: 2010-05-18 10:07 UTC by Omer Frenkel
Modified: 2015-10-27 23:55 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2012-08-09 08:02:55 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
console log (254.94 KB, application/x-compressed-tar)
2012-01-26 13:43 UTC, Avi Tal
no flags Details

Description Omer Frenkel 2010-05-18 10:07:18 UTC
Description of problem:
separating the inactive status for storage domain to inactive and maintenance,
maintenance - the user moved the domain to maintenance
inactive - the domain is inactive due to a problem

for more details: BZ 592745

Comment 1 Yaniv Kaul 2010-06-08 20:06:54 UTC
If I could just understand why maintenance should be different than detach.
We have too many states, which the user does not even understand the difference between.

Comment 2 Ayal Baron 2010-06-09 06:04:41 UTC
detached - the domain is not part of any storage pool / DC
inactive - the domain is not accessible (failure of some kind), if it is sorted out, it should be automatically activated without user intervention
maintenance - the domain should not be accessed even if it is accessible (user stated that the domain should not be used right now) - but it cannot be attached to a different DC.
active - everything is fine

If you want to reduce the number of states then it's fine by me to unite detach and maintenance.

Comment 3 lpeer 2011-02-07 07:41:43 UTC
This RFE is influencing the BE ability for automatic recovery.
In the current status when a storage domain is Inactive there is no indication if it is as result of an error or if the user put it to maintenance and the domain should not be accessed.

I would give this a high priority because we encountered many issues that could not be fixed because of this.

Comment 4 Avi Tal 2012-01-26 13:42:44 UTC
Jenkins has found a scenario where this patch isn't working:

Deactivating an ExportDomain turn to maintenance but then to inactive, just like the old design.
please check the following rest logs to follow the real deactivate process:

After running some manual tests on jenkins, i found out that this bug reproduce only on Export domain and ISO domain

Comment 5 Avi Tal 2012-01-26 13:43:41 UTC
Created attachment 557671 [details]
console log

Comment 6 Yaniv Kaul 2012-01-26 14:28:39 UTC
How is the bug in MODIFIED state without a link to a patch?

Comment 8 Itamar Heim 2012-08-09 08:02:55 UTC
closing ON_QA bugs as oVirt 3.1 was released:

Comment 9 Itamar Heim 2012-08-09 08:03:51 UTC
closing ON_QA bugs as oVirt 3.1 was released:

Note You need to log in before you can comment on or make changes to this bug.