Bug 769511 - Unable to remove VM that is in an "unknown" state
Summary: Unable to remove VM that is in an "unknown" state
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: oVirt
Classification: Retired
Component: ovirt-engine-core
Version: unspecified
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
: ---
Assignee: Roy Golan
QA Contact:
URL:
Whiteboard: virt
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-12-21 06:10 UTC by Brett Thurber
Modified: 2012-05-21 11:07 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-05-21 11:07:52 UTC
oVirt Team: ---


Attachments (Terms of Use)
vdsm.log from host in the affected data center (7.46 MB, application/octet-stream)
2011-12-21 06:10 UTC, Brett Thurber
no flags Details

Description Brett Thurber 2011-12-21 06:10:07 UTC
Created attachment 548983 [details]
vdsm.log from host in the affected data center

Description of problem:
Back end storage hosting the virtual machine experienced an unexpected outage causing a running VM to enter an unknown state.

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

How reproducible:
Unknown

Steps to Reproduce:
1.  Running VM
2.  Associated storage domain unexpectedly went off-line
3.  Hosted VM entered an "unknown" state and is unmanageable
  
Actual results:
Unable to start, stop, shutdown or delete VM.  Unable to execute a destroy on the associated storage domain.  

Utilizing the REST API to force VM delete results in the following error:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?><fault><reason>Operation Failed</reason><detail>[Cannot remove VM. VM is running.]</detail></fault>

Command executed:
curl -X DELETE -H "Accept: application/xml" -H "Content-Type: application/xml" -u admin@internal:xxxxxx -k -d "<action><force>true</force></action>" https://rhevm3-beta:8443/api/vms/3461f1fe-d2a4-4f9f-beda-5e360967e8ba

Error when trying to execute a destroy action ont eh storage domain:
Cannot destroy Storage. Storage status illegal.

Expected results:
Expect through the management portal the ability to remove a defunct VM and/or it's associated storage domain.  REST API should also allow forceful VM deletion regardless of VM state.

Additional info:
vdsm.log attached.

Comment 1 Roy Golan 2012-05-21 11:07:52 UTC

we can't destory a VM if we can't reachout to the domain to remove its disks but we do have auto-recovary that will make the domain and host responsive again (once outage ends) and this will let you manage the VM again.


Note You need to log in before you can comment on or make changes to this bug.