Bug 1299896 - Alias not found for device type graphics during migration at destination host error in vdsm log while migrating VM between 3.5 hosts in 3.6 engine
Summary: Alias not found for device type graphics during migration at destination host...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Virt
Version: 3.6.2.5
Hardware: x86_64
OS: Linux
unspecified
low vote
Target Milestone: ---
: ---
Assignee: Michal Skrivanek
QA Contact: Ilanit Stein
URL:
Whiteboard: virt
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-01-19 13:52 UTC by Michael Burman
Modified: 2016-01-29 14:15 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-01-29 14:15:39 UTC
oVirt Team: Virt
mburman: planning_ack?
mburman: devel_ack?
mburman: testing_ack?

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

Description Michael Burman 2016-01-19 13:52:39 UTC 
Description of problem:
Alias not found for device type graphics during migration at destination host error in vdsm log while migrating VM between 3.5 hosts in 3.6 engine. 

The next error appears in vdsm log while migrating a VM in cluster 3.5 between 2 servers with vdsm 3.5 (vdsm 4.16.32) in a 3.6 engine -->

Thread-305::ERROR::2016-01-19 06:12:16,360::vm::5764::vm.Vm::(_updateDevicesDomxmlCache) vmId=`4552036a-58a1-41b6-af8f-cd0dcb5aa003`::Alias not found for device type graphics during migration at destination host

Version-Release number of selected component (if applicable):
3.6.2.5-0.1.el6
vdsm-4.16.32
Comment 1 Michal Skrivanek 2016-01-29 14:15:39 UTC 
it's a harmless 3.5 problem
we won't be fixing 3.5 code anymore, so, as long as it's not happening to 3.6 vdsms we're good
Note You need to log in before you can comment on or make changes to this bug.