Bug 1028502 - don't log failed migration action from REST API in Events
Summary: don't log failed migration action from REST API in Events
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine
Version: 3.3.0
Hardware: Unspecified
OS: Unspecified
medium
unspecified
Target Milestone: ---
: 3.5.0
Assignee: Arik
QA Contact:
URL:
Whiteboard: virt
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-11-08 15:45 UTC by David Jaša
Modified: 2014-06-22 14:09 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-06-22 14:09:50 UTC
oVirt Team: ---
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description David Jaša 2013-11-08 15:45:21 UTC 
Description of problem:
don't log failed migration action from REST API in Events. Similar action such as shutting down VM in down status are not logged either

Version-Release number of selected component (if applicable):
is21:
rhevm-backend-3.3.0-0.31.beta1.el6ev.noarch
rhevm-restapi-3.3.0-0.31.beta1.el6ev.noarch

How reproducible:
always

Steps to Reproduce:
1. issue "POST /api/vms/UUID/migrate '<action/>'"
2. issue "POST /api/vms/UUID/migrate '<action/>'" again while VM is still migrating
3. look to Events

Actual results:
two "Migration Started" messages are logged

Expected results:
just first "Migration Started" message is logged (the one that actually results in migration)

Additional info:
Comment 1 Arik 2014-06-22 14:09:50 UTC 
VM is now locked while it is migrated so there's no chance anymore that migrate command will start while another one is executing for the same VM.
Note You need to log in before you can comment on or make changes to this bug.