Bug 1512572
| Summary: | vdsm Failed to connect to guest agent channel | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [oVirt] vdsm | Reporter: | Michael Burman <mburman> | ||||
| Component: | Core | Assignee: | Milan Zamazal <mzamazal> | ||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Michael Burman <mburman> | ||||
| Severity: | urgent | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 4.20.4 | CC: | amusil, bugs, danken, lzitnits, mburman, michal.skrivanek, mlehrer, mzamazal, ncredi, tjelinek | ||||
| Target Milestone: | ovirt-4.2.0 | Keywords: | AutomationBlocker, Regression | ||||
| Target Release: | --- | Flags: | rule-engine:
ovirt-4.2+
rule-engine: blocker+ |
||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2017-12-20 10:43:37 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: |
|
||||||
logs? (In reply to Michal Skrivanek from comment #1) > logs? I already spoke with Milan and he is aware of this report, also think that he already has a possible fix for it. Attaching vdsm logs, let me know if more are needed. Created attachment 1351789 [details]
vdsm logs
*** Bug 1513001 has been marked as a duplicate of this bug. *** Verified on - vdsm-4.20.8-29.git6ceb389.el7.centos.x86_64 This bugzilla is included in oVirt 4.2.0 release, published on Dec 20th 2017. Since the problem described in this bug report should be resolved in oVirt 4.2.0 release, published on Dec 20th 2017, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report. *** Bug 1507939 has been marked as a duplicate of this bug. *** I'm still seeing this all the time. Specifically, with hosted-engine. See http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-master/276/ - log @ http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-master/276/artifact/exported-artifacts/test_logs/hc-basic-suite-master/post-002_bootstrap.py/lago-hc-basic-suite-master-host-0/_var_log/vdsm/vdsm.log : 2018-04-02 09:58:05,485-0400 INFO (vm/96a15386) [virt.vm] (vmId='96a15386-2397-45fd-b739-e7b96c8f31a5') Starting connection (guestagent:250) 2018-04-02 09:58:05,486-0400 ERROR (vm/96a15386) [virt.vm] (vmId='96a15386-2397-45fd-b739-e7b96c8f31a5') Failed to connect to guest agent channel (vm:2462) Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/vdsm/virt/vm.py", line 2460, in _vmDependentInit self.guestAgent.start() File "/usr/lib/python2.7/site-packages/vdsm/virt/guestagent.py", line 251, in start self._prepare_socket() File "/usr/lib/python2.7/site-packages/vdsm/virt/guestagent.py", line 293, in _prepare_socket supervdsm.getProxy().prepareVmChannel(self._socketName) File "/usr/lib/python2.7/site-packages/vdsm/common/supervdsm.py", line 55, in __call__ return callMethod() File "/usr/lib/python2.7/site-packages/vdsm/common/supervdsm.py", line 53, 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/96a15386-2397-45fd-b739-e7b96c8f31a5.com.redhat.rhevm.vdsm' 2018-04-02 09:58:05,488-0400 INFO (vm/96a15386) [virt.vm] (vmId='96a15386-2397-45fd-b739-e7b96c8f31a5') CPU running: domain initialization (vm:6065) There is no ovirt-guest-agent channel in HostedEngineLocal domain XML. So when the VM is recovered on Vdsm start, the fallback backwards compatible channel path is used as the socket name. The socket doesn't exist (there is no ovirt-guest-agent around) and the error above is raised on attempt to open it. |
Description of problem: vdsm Failed to connect to guest agent channel 2017-11-13 16:19:04,634+0200 INFO (vm/960acdbb) [virt.vm] (vmId='960acdbb-69f1-4071-b10b-410b47cd6a84') Starting connection (guestagent:244) 2017-11-13 16:19:04,635+0200 ERROR (vm/960acdbb) [virt.vm] (vmId='960acdbb-69f1-4071-b10b-410b47cd6a84') 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/960acdbb-69f1-4071-b10b-410b47cd6a84.com.redhat.rhevm.vdsm' MainProcess|vm/960acdbb::DEBUG::2017-11-13 16:19:04,635::supervdsm_server::90::SuperVdsm.ServerCallback::(wrapper) call prepareVmChannel with () {} MainProcess|vm/960acdbb::ERROR::2017-11-13 16:19:04,635::supervdsm_server::94::SuperVdsm.ServerCallback::(wrapper) Error in prepareVmChannel Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/vdsm/supervdsm_server.py", line 92, in wrapper res = func(*args, **kwargs) File "/usr/lib/python2.7/site-packages/vdsm/supervdsm_api/virt.py", line 35, in prepareVmChannel fsinfo = os.stat(socketFile) OSError: [Errno 2] No such file or directory: '/var/lib/libvirt/qemu/channels/960acdbb-69f1-4071-b10b-410b47cd6a84.com.redhat.rhevm.vdsm' Version-Release number of selected component (if applicable): vdsm-4.20.6-62.gitd3023e4.el7.centos.x86_64 How reproducible: 100% Steps to Reproduce: 1. Run VM on latest vdsm 4.2, the guest should have a guest-agent installed and running Actual results: vdsm failed to connect to guest agent channel Expected results: Should work as expected