Bug 1475893
Summary: | DR (site to site) - Add the ability to support force remove of last master storage domain from data center | ||
---|---|---|---|
Product: | [oVirt] ovirt-engine | Reporter: | Maor <mlipchuk> |
Component: | Backend.Core | Assignee: | Maor <mlipchuk> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Elad <ebenahar> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 4.2.0 | CC: | amureini, apinnick, bugs, ylavi |
Target Milestone: | ovirt-4.2.0 | Keywords: | Improvement, SubTask |
Target Release: | --- | Flags: | rule-engine:
ovirt-4.2+
gklein: testing_plan_complete- |
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: |
The Engine now allows forcibly removing the last master storage domain from the Data Center. The Data Center's status changes to "Uninitialized."
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2017-12-20 10:44:40 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: | |||
Bug Depends On: | |||
Bug Blocks: | 1548852 |
Description
Maor
2017-07-27 14:43:11 UTC
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release. Last storage domain destroy is now possible without data center removal. Used: ovirt-engine-4.2.0-0.0.master.20170904111624.git842d79b.el7.centos.noarch The documentation text flag should only be set after 'doc text' field is provided. Please provide the documentation text and set the flag to '?' again. 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. |