Bug 1043627 - Exception in agent.log after hosted vm migration
Summary: Exception in agent.log after hosted vm migration
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-hosted-engine-ha
Version: 3.3.0
Hardware: Unspecified
OS: Linux
unspecified
unspecified
Target Milestone: ---
: 3.6.0
Assignee: Doron Fediuck
QA Contact: Artyom
URL:
Whiteboard: sla
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-16 18:31 UTC by Artyom
Modified: 2016-02-10 20:15 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-09-24 08:01:06 UTC
oVirt Team: SLA
Target Upstream Version:

Attachments (Terms of Use)
logs (261.52 KB, application/zip)
2013-12-16 18:31 UTC, Artyom 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Artyom 2013-12-16 18:31:24 UTC 
Created attachment 837369 [details]
logs

Description of problem:
After hosted-engine vm migration, appear exception in agent.log 
Traceback (most recent call last):
  File "/usr/lib/python2.6/site-packages/ovirt_hosted_engine_ha/agent/hosted_engine.py", line 1350, in _handle_migrate_monitor
    vm_id,
  File "/usr/lib/python2.6/site-packages/ovirt_hosted_engine_ha/lib/vds_client.py", line 85, in run_vds_client_cmd
    response['status']['message'])
DetailedError: Error 1 from migrateStatus: Virtual machine does not exist

Version-Release number of selected component (if applicable):
ovirt-hosted-engine-ha-0.1.0-0.9.rc.el6ev.noarch

How reproducible:
Always

Steps to Reproduce:
1. Finish deploy process on two hosts(hosted-engine --deploy)
2. Migrate manually hosted-engine vm via UI
3.

Actual results:
Migration finish success, but appear new exception in agent.log

Expected results:
Migration finish success, without any exceptions in agent.log 


Additional info:
Comment 1 Greg Padgett 2013-12-17 12:34:01 UTC 
Note that the exception here is harmless.  The agent on the migration source host expects to see a "migration done" status which won't show up in certain cases (engine-initiated migration), but by this point the vm is gone and the agent switches to "off" state anyway as it should.
Comment 2 Jiri Moskovcak 2014-07-17 07:41:44 UTC 
Are you still able to reproduce it with the current versions?
Comment 3 Artyom 2014-07-17 10:11:30 UTC 
Not tried, if you want I can try it on newer version of 3.4.
Comment 4 Jiri Moskovcak 2014-07-17 10:13:09 UTC 
(In reply to Artyom from comment #3)
> Not tried, if you want I can try it on newer version of 3.4.

Yes please.
Comment 5 Artyom 2014-07-17 14:44:12 UTC 
Still receive this one on source host:
MainThread::ERROR::2014-07-17 17:42:34,094::hosted_engine::763::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(_monitor_migration) Failed to migrate
Traceback (most recent call last):
  File "/usr/lib/python2.6/site-packages/ovirt_hosted_engine_ha/agent/hosted_engine.py", line 759, in _monitor_migration
    vm_id,
  File "/usr/lib/python2.6/site-packages/ovirt_hosted_engine_ha/lib/vds_client.py", line 85, in run_vds_client_cmd
    response['status']['message'])
DetailedError: Error 1 from migrateStatus: Virtual machine does not exist

ovirt-hosted-engine-ha-1.1.2-5.el6ev.noarch
Comment 6 Doron Fediuck 2014-11-17 16:46:09 UTC 
Since this is harmless, pushing forward.
Note You need to log in before you can comment on or make changes to this bug.