Bug 1513001

Summary: Guest agent fails to report IP address of running VMs
Product: [oVirt] ovirt-engine Reporter: Lilach Zitnitski <lzitnits>
Component: BLL.VirtAssignee: Michal Skrivanek <michal.skrivanek>
Status: CLOSED DUPLICATE QA Contact: meital avital <mavital>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 4.2.0CC: bugs, pmatyas, ratamir
Target Milestone: ---Keywords: Automation, AutomationBlocker, Regression
Target Release: ---Flags: rule-engine: ovirt-4.2+
rule-engine: blocker+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-11-15 06:38:29 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Virt RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
logs none

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 ***