Bug 893573 - [RHEVM] Get error during close SPICE Console windows - Cannot get vdsManager for vdsid=00000000-0000-0000-0000-000000000000
Summary: [RHEVM] Get error during close SPICE Console windows - Cannot get vdsManager...
Keywords:
Status: CLOSED DUPLICATE of bug 868297
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine
Version: 3.2.0
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
: 3.2.0
Assignee: Roy Golan
QA Contact: vvyazmin@redhat.com
URL:
Whiteboard: virt
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-01-09 13:39 UTC by vvyazmin@redhat.com
Modified: 2013-02-21 08:08 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-02-21 08:08:00 UTC
oVirt Team: ---
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
## Logs rhevm (2.12 MB, application/octet-stream)
2013-01-09 13:39 UTC, vvyazmin@redhat.com
no flags Details


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 10770 0 None None None Never

Description vvyazmin@redhat.com 2013-01-09 13:39:50 UTC
Created attachment 675550 [details]
## Logs rhevm

Description of problem:
Get error during close SPICE Console windows

Version-Release number of selected component (if applicable):
RHEVM 3.2 - SF03 environment 

RHEVM: rhevm-3.2.0-4.el6ev.noarch
VDSM: vdsm-4.10.2-3.0.el6ev.x86_64
LIBVIRT: libvirt-0.10.2-13.el6.x86_64
QEMU & KVM: qemu-kvm-rhev-0.12.1.2-2.348.el6.x86_64
SANLOCK: sanlock-2.6-2.el6.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Open SPICE Console windows
2. Close SPICE Console windows
  
Actual results:
In /var/log/ovirt-engine/engine.log get error:
Cannot get vdsManager for vdsid=00000000-0000-0000-0000-000000000000

Expected results:
No exception should be found

Additional info:

/var/log/ovirt-engine/engine.log
2013-01-09 17:22:11,504 WARN  [org.ovirt.engine.core.dal.job.ExecutionMessageDirector] (ajp-/127.0.0.1:8702-4) [7eee8509] The message key UpdateVmConsoleData is missing from bundles/ExecutionMessages
2013-01-09 17:22:11,616 INFO  [org.ovirt.engine.core.bll.UpdateVmConsoleDataCommand] (ajp-/127.0.0.1:8702-4) [7eee8509] Running command: UpdateVmConsoleDataCommand internal: false. Entities affected :  ID: 509916a2-0be4-480c-8c9a-a2427c74f0a2 Type: VM
2013-01-09 17:22:11,616 ERROR [org.ovirt.engine.core.vdsbroker.ResourceManager] (ajp-/127.0.0.1:8702-4) [7eee8509] Cannot get vdsManager for vdsid=00000000-0000-0000-0000-000000000000
2013-01-09 17:22:11,618 INFO  [org.ovirt.engine.core.vdsbroker.UpdateVmDynamicDataVDSCommand] (ajp-/127.0.0.1:8702-4) [7eee8509] START, UpdateVmDynamicDataVDSCommand( HostId = 00000000-0000-0000-0000-000000000000, vmDynamic=org.ovirt.engine.core.common.businessentities.VmDynamic@99145e55), log id: 50eed693
2013-01-09 17:22:11,618 INFO  [org.ovirt.engine.core.vdsbroker.UpdateVmDynamicDataVDSCommand] (ajp-/127.0.0.1:8702-4) [7eee8509] FINISH, UpdateVmDynamicDataVDSCommand, log id: 50eed693


/var/log/vdsm/vdsm.log

Comment 4 Roy Golan 2013-02-10 09:14:28 UTC
depends on 868297

The UpdateVmConsoleData command has been removed since the console data is being updated by vds monitoring.


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