Bug 819279 - ovirt-engine-backend [TEXT]: trying to destroy an active domain will give an error that the domain is unknown and not active
Summary: ovirt-engine-backend [TEXT]: trying to destroy an active domain will give an ...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine
Version: 3.1.0
Hardware: x86_64
OS: Linux
low
low
Target Milestone: ---
: 3.1.0
Assignee: Tal Nisan
QA Contact: vvyazmin@redhat.com
URL:
Whiteboard: storage
: 818192 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-05-06 09:11 UTC by Dafna Ron
Modified: 2016-02-10 16:38 UTC (History)
10 users (show)

Fixed In Version: SI8
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-12-04 20:06:39 UTC
oVirt Team: Storage
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
log (22.04 KB, application/x-xz)
2012-05-06 09:11 UTC, Dafna Ron
no flags Details

Description Dafna Ron 2012-05-06 09:11:38 UTC
Created attachment 582409 [details]
log

Description of problem:

trying to destroy an active SD will give the following error: 

Error: Cannot destroy Storage. Storage status is unknown.
-Please check Storage Domain and retry the operation.

please change error message to include other SD states 
also, we should be able to destroy the domain in unknown state.

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

si3

How reproducible:

100%

Steps to Reproduce:
1. try to destroy and active domain 
2.
3.
  
Actual results:

we get an error that storage domain is unknown 

Expected results:

we should include all states in the error

Additional info: log 

2012-05-06 11:26:17,306 WARN  [org.ovirt.engine.core.bll.storage.ForceRemoveStorageDomainCommand] (ajp--0.0.0.0-8009-3) CanDoAction of action ForceRemoveStorageDomain failed. Reasons:VAR__ACTION__DESTROY_DOMAIN,VAR__TYPE__STORAGE__DOMAIN,ACTION_TYPE_FAILED_STORAGE_DOMAIN_STATUS_ILLEGAL2

Comment 1 Tal Nisan 2012-06-11 19:42:22 UTC
http://gerrit.ovirt.org/5260

Comment 2 Tal Nisan 2012-06-13 13:57:30 UTC
Commit b05469388b690b8beb93070bbe77738637aafa25

Comment 3 vvyazmin@redhat.com 2012-06-26 14:22:24 UTC
This BUG reproduced on RHEVM 3.1 - SI7 


RHEV-M: rhevm-3.1.0-2.el6ev.noarch
VDSM: vdsm-4.9.6-17.0.el6.x86_64
LIBVIRT: libvirt-0.9.10-21.el6.x86_64
QEMV & KVM: qemu-kvm-rhev-0.12.1.2-2.295.el6.x86_64

Comment 4 Tal Nisan 2012-06-26 14:24:42 UTC
You don't get the correct status in the message?

Comment 5 vvyazmin@redhat.com 2012-07-09 13:24:02 UTC
Verified on RHEVM 3.1 - SI9.1 

RHEV-M: rhevm-3.1.0-5.el6ev.noarch
VDSM: vdsm-4.9.6-17.0.el6.x86_64
LIBVIRT: libvirt-0.9.10-21.el6.x86_64
QEMV & KVM: qemu-kvm-rhev-0.12.1.2-2.295.el6.x86_64

Comment 6 Allon Mureinik 2012-09-30 06:00:37 UTC
*** Bug 818192 has been marked as a duplicate of this bug. ***


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