Bug 798707 - [ovirt] [vdsm] migration: vm status stuck on 'migrationDestination' for several minutes altough vm is running on libvirt
Summary: [ovirt] [vdsm] migration: vm status stuck on 'migrationDestination' for seve...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: oVirt
Classification: Retired
Component: vdsm
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ---
Assignee: Dan Kenigsberg
QA Contact:
URL:
Whiteboard: virt
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-02-29 16:03 UTC by Haim
Modified: 2014-01-13 00:51 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-08-19 10:18:17 UTC
oVirt Team: ---


Attachments (Terms of Use)
vdsm log (17.02 KB, application/x-gzip)
2012-02-29 16:05 UTC, Haim
no flags Details

Description Haim 2012-02-29 16:03:08 UTC
Description of problem:

- run vm with os installed 
- migrate vm from host A to host B 
- VM moves to state: unknown '?' for several minutes
- VM moves to state UP

notes:

when I query the logs, I see that vmGetStats is sent on vm and vdsm returns the following for 4-5 minutes: 

Thread-3998::DEBUG::2012-02-29 17:46:19,596::BindingXMLRPC::854::vds::(wrapper) return vmGetStats with {'status': {'message': 'Done', 'code': 0}, 'statsList': [{'status': 'Migration Destination', 'hash': '0', 'acpiEnable': 'true', 'pid'
Thread-4002::DEBUG::2012-02-29 17:46:21,617::BindingXMLRPC::848::vds::(wrapper) client [10.35.97.30]::call vmGetStats with ('52cb68fd-00bb-4dbe-a17c-b63c372daf16',) {} flowID [93b8240]

please note that during that time, vm status is running on libvirt. 

git hash: cc3662eb4c59a4c68577828beeebbcb5fbf93f96

Comment 1 Haim 2012-02-29 16:05:44 UTC
Created attachment 566579 [details]
vdsm log

Comment 2 Dan Kenigsberg 2012-04-18 20:45:15 UTC
reproduciblity? how often is this?

Comment 3 Michal Skrivanek 2013-08-19 10:18:17 UTC
doesn't seem to be happening anymore. There were a lot of monitoring-related changes in engine in the meantime. 
Please reopen if still relevant and supply engine log


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