Bug 1057156

Summary:	last master storage cannot be detached
Product:	[oVirt] ovirt-engine	Reporter:	Petr Beňas <pbenas>
Component:	Frontend.WebAdmin	Assignee:	Liron Aravot <laravot>
Status:	CLOSED WONTFIX	QA Contact:	Raz Tamir <ratamir>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	---	CC:	acanan, amureini, bugs, gklein, mgoldboi, pbenas, pstehlik, rbalakri, srevivo, ykaul, ylavi
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-02-07 15:09:47 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:	1080372, 1185830
Bug Blocks:

Description Petr Beňas 2014-01-23 14:36:02 UTC

Description of problem:


Version-Release number of selected component (if applicable):
 oVirt Engine Version: 3.4.0-0.5.beta1.fc19 

How reproducible:
100%

Steps to Reproduce:
1. add one nfs storage
2. attempt to remove it

Actual results:
After removal of destroying the domain following error is shown:
Error while executing action: Cannot destroy the master Storage Domain from the Data Center without another active Storage Domain to take its place.
-Either activate another Storage Domain in the Data Center, or remove the Data Center.
-If you have problems with the master Data Domain, consider following the recovery process described in the documentation, or contact your system administrator.

Expected results:
It should be possible to remove the master storage domain when it's empty. It makes sense to refuse removal if data such as virtual disks would be lost, but makes no sense with empty domain. 

Additional info:

Comment 1 Itamar Heim 2014-01-26 08:10:20 UTC

Setting target release to current version for consideration and review. please
do not push non-RFE bugs to an undefined target release to make sure bugs are
reviewed for relevancy, fix, closure, etc.

Comment 2 Liron Aravot 2014-08-18 10:50:22 UTC

Allon,
from a brief look - this change isn't that trivial (more like a RFE than a bug). Do we want to handle that for 3.5 or to wait to the expected changes on those areas in 3.6?

Comment 3 Allon Mureinik 2014-08-18 12:42:08 UTC

(In reply to Liron Aravot from comment #2)
> Allon,
> from a brief look - this change isn't that trivial (more like a RFE than a
> bug). Do we want to handle that for 3.5 or to wait to the expected changes
> on those areas in 3.6?
Let's re-consider after removing the master domain (RFE 1080372)

Comment 5 Sandro Bonazzola 2015-09-04 08:58:29 UTC

This is an automated message.
This Bugzilla report has been opened on a version which is not maintained anymore.
Please check if this bug is still relevant in oVirt 3.5.4.
If it's not relevant anymore, please close it (you may use EOL or CURRENT RELEASE resolution)
If it's an RFE please update the version to 4.0 if still relevant.

Comment 6 Aharon Canan 2015-09-08 12:22:32 UTC

Not sure if we want to handle it.
Master domain will be removed soon anyway.

Allon - yours.

Comment 7 Allon Mureinik 2015-09-08 14:28:26 UTC

(In reply to Aharon Canan from comment #6)
> Not sure if we want to handle it.
> Master domain will be removed soon anyway.
> 
> Allon - yours.
Pushing out to 4.0 to re-asses.

Comment 8 Red Hat Bugzilla Rules Engine 2015-10-19 10:54: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.

Comment 9 Yaniv Lavi 2017-02-07 15:09:47 UTC

Didn't get any user issues on this.
Closing as this is being less relevant with roadmap plans.