Bug 918463

Summary: After storage server shutdown, no way to clear single host, datacenter and storage domain via GUI
Product: Red Hat Enterprise Virtualization Manager Reporter: Ilanit Stein <istein>
Component: ovirt-engineAssignee: Barak <bazulay>
Status: CLOSED DUPLICATE QA Contact:
Severity: medium Docs Contact:
Priority: unspecified    
Version: 3.2.0CC: acathrow, dyasny, iheim, lpeer, Rhev-m-bugs, sgrinber, yeylon, ykaul, yzaslavs
Target Milestone: ---Keywords: Triaged
Target Release: 3.2.0Flags: abaron: Triaged+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: infra
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-03-13 09:51:02 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Infra RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
engine.log
none
vdsm log 1
none
vdsm log 2 none

Description Ilanit Stein 2013-03-06 09:59:16 UTC 
Description of problem:

Following storage server shutdown, host, nfs data center, and data storage doamin elements, existing in a setup, cannot be removed. 
Please add a means for the user to be able to remove these elements via GUI. 

More details:

Host state is spm/non-responsive, and cannot move to maintanance. data center/storage doamin cannot be force removed.

We have ways to do the removal, but there are not "user friendly":
1. data base intervention,
2. Adding a host from the same type of the existing one, so it would fit the cluster properties.

Version-Release number of selected component (if applicable):

sf-8
Comment 1 Ilanit Stein 2013-03-06 10:31:26 UTC 
Additional info: The host was single in the data center.
Comment 2 Ayal Baron 2013-03-06 12:19:11 UTC 
Issue here is the host cannot be moved to maintenance.
I believe Kublin had a bug on this, possibly a duplicate?
Comment 3 Ilanit Stein 2013-03-06 13:40:39 UTC 
Created attachment 705941 [details]
engine.log
Comment 4 Ilanit Stein 2013-03-06 13:44:20 UTC 
Created attachment 705943 [details]
vdsm log 1
Comment 5 Ilanit Stein 2013-03-06 13:44:47 UTC 
Created attachment 705944 [details]
vdsm log 2
Comment 6 mkublin 2013-03-11 07:43:45 UTC 
The following commit d635e72d9558f10f4dee5e58ed9fe37afcecd3a6 is disabling remove of data centrer when not all it's hosts are in maintenance mode.
The following commit was tried to solve a bug #850286, in Comment 9 software developer Kublin ask question why disable force remove when not all it's hosts are in maintenance mode?
Now, this is a case, so bug should be closed as worked as expected?

Moving to storage, any my fix will cause a regression to fix of bug #850286,
it is mean that any my patch will got -1, as causing regression.
Comment 7 Ayal Baron 2013-03-11 21:03:53 UTC 
Ilanit, you can (manually) fence the host and then move to maintenance.
If you're fine with destroying the DC then there shouldn't be any VMs on the host (at least any that you care about).
If you succeed with above then indeed I would close this as not a bug (force delete is an extreme measure that should not be so easy to do)
Comment 8 Ayal Baron 2013-03-13 09:45:12 UTC 
After discussing with Haim, problem is that currently we do not allow to manual fence a host when there isn't another host (probably a dup).
This is an infra issue
Comment 9 Simon Grinberg 2013-03-13 09:51:02 UTC 

*** This bug has been marked as a duplicate of bug 837539 ***