Bug 947849 - engine: unable to resume paused VMs when host in stuck on preparing for maintenance: Error while executing action: Cannot run VM. Operation can be performed only when Host status is Up
Summary: engine: unable to resume paused VMs when host in stuck on preparing for maint...
Keywords:
Status: CLOSED DUPLICATE of bug 885994
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine
Version: 3.1.3
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
: 3.2.0
Assignee: Roy Golan
QA Contact: Pavel Stehlik
URL:
Whiteboard: virt
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-04-03 12:22 UTC by Haim
Modified: 2015-09-22 13:10 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-04-10 05:42:18 UTC
oVirt Team: ---
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
all logs. (3.57 MB, application/x-tar)
2013-04-03 12:28 UTC, Haim 		no flags Details
View All

Description Haim 2013-04-03 12:22:48 UTC 
Description of problem:

have an host with 4 vms running, host state is prepare for maintenance, vms goes into paused state, when I try to resume the vms, I get the following error message: 


Error while executing action: Cannot run VM. Operation can be performed only when Host status is Up.

expected results:

1) should be able to resume the vms
Comment 1 Haim 2013-04-03 12:28:55 UTC 
Created attachment 731127 [details]
all logs.
Comment 2 Haim 2013-04-03 12:29:20 UTC 
look for:

2013-04-03 13:14:20,613 WARN  [org.ovirt.engine.core.bll.RunVmCommand] (http-/0.0.0.0:8443-26) CanDoAction of action RunVm failed. Reasons:VAR__ACTION__RUN,VAR
__TYPE__VM,VAR__HOST_STATUS__UP,ACTION_TYPE_FAILED_VDS_STATUS_ILLEGAL
Comment 3 Michal Skrivanek 2013-04-04 10:33:33 UTC 
i propose we allow it to be resumed when paused
Comment 4 Haim 2013-04-08 19:31:12 UTC 
re-opening (last status doesn't make sense).
Comment 5 Roy Golan 2013-04-10 05:42:18 UTC 

*** This bug has been marked as a duplicate of bug 885994 ***
Note You need to log in before you can comment on or make changes to this bug.