Bug 1513001 - Guest agent fails to report IP address of running VMs
Summary: Guest agent fails to report IP address of running VMs
Keywords:
Status: CLOSED DUPLICATE of bug 1512572
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Virt
Version: 4.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: ---
: ---
Assignee: Michal Skrivanek
QA Contact: meital avital
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-11-14 15:02 UTC by Lilach Zitnitski
Modified: 2019-04-28 14:03 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2017-11-15 06:38:29 UTC
oVirt Team: Virt
Embargoed:
rule-engine: ovirt-4.2+
rule-engine: blocker+


Attachments (Terms of Use)
logs (304.29 KB, application/zip)
2017-11-14 15:06 UTC, Lilach Zitnitski
no flags Details

Description Lilach Zitnitski 2017-11-14 15:02:52 UTC
Description of problem:
When staring VM, the ip address of the guest does not show in the UI even after more than 10 minutes. 
When connecting to console the guest agent service is running and the network is fine. 
vdsm log is showing error "Failed to connect to guest agent channel"

Version-Release number of selected component (if applicable):
ovirt-engine-4.2.0-0.0.master.20171113223918.git25568c3.el7.centos.noarch
vdsm-4.20.6-62.gitd3023e4.el7.centos.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Start vm
2. Wait for IP to appear in the UI
3.

Actual results:
The guest fails to report ip addresses 

Expected results:
The ip address should be seen in the right place in the webadmin

Additional info:

2017-11-14 16:40:01,440+0200 ERROR (vm/dbfe2305) [virt.vm] (vmId='dbfe2305-af54-462a-b253-28d3e42dae6f') Failed to connect to guest agent channel (vm:2364)
Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/vdsm/virt/vm.py", line 2362, in _vmDependentInit
    self.guestAgent.start()
  File "/usr/lib/python2.7/site-packages/vdsm/virt/guestagent.py", line 245, in start
    self._prepare_socket()
  File "/usr/lib/python2.7/site-packages/vdsm/virt/guestagent.py", line 287, in _prepare_socket
    supervdsm.getProxy().prepareVmChannel(self._socketName)
  File "/usr/lib/python2.7/site-packages/vdsm/supervdsm.py", line 53, in __call__
    return callMethod()
  File "/usr/lib/python2.7/site-packages/vdsm/supervdsm.py", line 51, in <lambda>
    **kwargs)
  File "<string>", line 2, in prepareVmChannel
  File "/usr/lib64/python2.7/multiprocessing/managers.py", line 773, in _callmethod
    raise convert_to_error(kind, result)
OSError: [Errno 2] No such file or directory: '/var/lib/libvirt/qemu/channels/dbfe2305-af54-462a-b253-28d3e42dae6f.com.redhat.rhevm.vdsm'

Comment 1 Lilach Zitnitski 2017-11-14 15:06:56 UTC
Created attachment 1352018 [details]
logs

Comment 2 Michal Skrivanek 2017-11-15 06:38:29 UTC

*** This bug has been marked as a duplicate of bug 1512572 ***


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