| Summary: | oVirt - Core: Inconsistent and confusing storage domain statuses | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Retired] oVirt | Reporter: | Daniel Paikov <dpaikov> | ||||
| Component: | ovirt-engine-core | Assignee: | lpeer <lpeer> | ||||
| Status: | CLOSED DUPLICATE | QA Contact: | Daniel Paikov <dpaikov> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | unspecified | CC: | acathrow, amureini, dron, hateya, iheim, lhornyak, mkublin, ykaul | ||||
| Target Milestone: | --- | ||||||
| Target Release: | 3.3.4 | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | storage | ||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | |||||||
| : | 829275 (view as bug list) | Environment: | |||||
| Last Closed: | 2012-06-12 07:25:22 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | Storage | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Attachments: |
|
||||||
According to ofrenkel, the fact that the SD is moved by backend to Inactive status is a bug. 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. *** This bug has been marked as a duplicate of bug 829275 *** |
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.