Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1151966

Summary: [RFE] Force removing a host from within the RHEV GUI
Product: Red Hat Enterprise Virtualization Manager Reporter: Nikolai Sednev <nsednev>
Component: ovirt-engineAssignee: Nobody <nobody>
Status: CLOSED WONTFIX QA Contact:
Severity: medium Docs Contact:
Priority: unspecified    
Version: 3.5.0CC: ecohen, gklein, iheim, lpeer, lsurette, masayag, oourfali, pkliczew, rbalakri, Rhev-m-bugs, yeylon
Target Milestone: ---Keywords: FutureFeature
Target Release: ---Flags: sherold: Triaged+
Hardware: x86_64   
OS: Linux   
Whiteboard: infra
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-11-25 17:29:35 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
enginelogs none

Description Nikolai Sednev 2014-10-13 08:35:05 UTC
Description of problem:
Force removing a host from within the RHEV GUI.
I have a host in RHEVM, which stays in non responsive state, while it's not SPM and not the single host in host cluster and I also have two more up and running other hosts in host cluster, but the non-responsive host can't be removed and it's remove field is greyed out. I've tried "host have been rebooted" and "Maintenance", nothing happens and host stays at the same state, so I can't remove it in any means.

Version-Release number of selected component (if applicable):
rhevm-3.5.0-0.14.beta.el6ev.noarch
libvirt-0.10.2-46.el6.x86_64
vdsm-4.16.6-1.el6ev.x86_64
qemu-kvm-rhev-0.12.1.2-2.448.el6.x86_64
sanlock-2.8-1.el6.x86_64


How reproducible:
50%.

Steps to Reproduce:
1.Please contact me to get more information from my setup.
2.
3.

Actual results:
Host in non-responsive state not being able to be removed.

Expected results:
Host should be transferred to maintenance and then removed. 

Additional info:
This topic was also discussed here with no final solution provided for my case: https://access.redhat.com/discussions/709773

Comment 1 Nikolai Sednev 2014-10-13 09:05:30 UTC
Created attachment 946285 [details]
enginelogs

Comment 3 Oved Ourfali 2015-11-25 17:29:35 UTC
No. 
In addition unless the user misuses the hosts and hack them in any way, he shouldn't get into such situation. 

Closing as wontfix. 
We've done some fixed and changes in the host life cycle since this RFE was opened. 

If there is still an issue please reopen and provide steps to reproduce.