Bug 788936 - oVirt - Core: Inconsistent and confusing storage domain statuses
Summary: oVirt - Core: Inconsistent and confusing storage domain statuses
Keywords:
Status: CLOSED DUPLICATE of bug 829275
Alias: None
Product: oVirt
Classification: Retired
Component: ovirt-engine-core
Version: unspecified
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 3.3.4
Assignee: lpeer
QA Contact: Daniel Paikov
URL:
Whiteboard: storage
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-02-09 10:31 UTC by Daniel Paikov
Modified: 2016-02-10 17:06 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 829275 (view as bug list)
Environment:
Last Closed: 2012-06-12 07:25:22 UTC
oVirt Team: Storage

Attachments (Terms of Use)
engine.log (4.66 KB, application/x-compressed-tar)
2012-02-09 10:31 UTC, Daniel Paikov 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Daniel Paikov 2012-02-09 10:31:18 UTC 
Created attachment 560500 [details]
engine.log

* If a non-master domain (including ISO and export) is deactivated by user, the domain goes to Maintenance status for a few seconds, and then goes to Inactive status.
* If a master data domain is deactivated by user, the domain goes into Maintenance status and doesn't go into Inactive status.
* These two statuses, Maintenance and Inactive, can co-exist in the same DC at the same time, even though they presumably mean the same thing.
Comment 1 Daniel Paikov 2012-02-09 13:16:59 UTC 
According to ofrenkel, the fact that the SD is moved by backend to Inactive status is a bug.
Comment 4 Laszlo Hornyak 2012-06-06 11:40:43 UTC 
Also got reports from Dafna and Haim, the autorecovery feature is kicking into the storage domain in 5 minutes, since it is moved to Inactive status instead of Maintenance. If this is the root cause, then maybe we should increase the priority.
Comment 5 mkublin 2012-06-12 07:25:22 UTC 

*** This bug has been marked as a duplicate of bug 829275 ***
Note You need to log in before you can comment on or make changes to this bug.