Bug 1080536
| Summary: | [vdsm] After VM is migrated - 'Failed to prepare vmchannel' issue visible in vdsm.log, VM cannot be put down | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Jiri Belka <jbelka> | ||||
| Component: | vdsm | Assignee: | Francesco Romani <fromani> | ||||
| Status: | CLOSED DUPLICATE | QA Contact: | meital avital <mavital> | ||||
| Severity: | urgent | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 3.2.0 | CC: | bazulay, gklein, iheim, lpeer, ofrenkel, yeylon | ||||
| Target Milestone: | --- | Keywords: | Reopened | ||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | virt | ||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2014-03-27 09:23:16 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
this looks very much like a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1052841 Internally, the VDSM flow is the same, and this code path was not changed significantly. *** This bug has been marked as a duplicate of bug 1052841 *** reopenend because different versions (this is 3.2) Confirmed root cause same of 1052841, fix would be the same. Will be just a matter of backporting. Sorry for the noise, re-closing. *** This bug has been marked as a duplicate of bug 1052841 *** |
Created attachment 878551 [details] vdsm.log Description of problem: After I migrated a VM from 3.3 host (vdsm-4.14.2-0.4.el6ev.x86_64) being part of 3.2 env/cluster to 3.2 host (vdsm-4.10.2-30.1.el6ev.x86_64), I cannot shutdown the VM. It is in Powering down state and then in Non Responding. ... Thread-640::DEBUG::2014-03-25 15:46:54,856::BindingXMLRPC::913::vds::(wrapper) client [10.34.63.76]::call vmDestroy with ('2237e47b-4b9b-4efb-a18b-0234ab15d22b',) {} flowID [4215a389] Thread-640::INFO::2014-03-25 15:46:54,857::API::310::vds::(destroy) vmContainerLock acquired by vm 2237e47b-4b9b-4efb-a18b-0234ab15d22b Thread-640::DEBUG::2014-03-25 15:46:54,857::libvirtvm::2618::vm.Vm::(destroy) vmId=`2237e47b-4b9b-4efb-a18b-0234ab15d22b`::destroy Called Thread-640::INFO::2014-03-25 15:46:54,857::libvirtvm::2567::vm.Vm::(releaseVm) vmId=`2237e47b-4b9b-4efb-a18b-0234ab15d22b`::Release VM resources Thread-640::DEBUG::2014-03-25 15:46:54,863::utils::353::vm.Vm::(stop) vmId=`2237e47b-4b9b-4efb-a18b-0234ab15d22b`::Stop statistics collection Thread-55::DEBUG::2014-03-25 15:46:54,863::utils::384::vm.Vm::(run) vmId=`2237e47b-4b9b-4efb-a18b-0234ab15d22b`::Stats thread finished Thread-640::ERROR::2014-03-25 15:46:54,863::BindingXMLRPC::932::vds::(wrapper) unexpected error Traceback (most recent call last): File "/usr/share/vdsm/BindingXMLRPC.py", line 918, in wrapper File "/usr/share/vdsm/BindingXMLRPC.py", line 194, in vmDestroy File "/usr/share/vdsm/API.py", line 315, in destroy File "/usr/share/vdsm/libvirtvm.py", line 2623, in destroy File "/usr/share/vdsm/libvirtvm.py", line 2575, in releaseVm File "/usr/share/vdsm/guestIF.py", line 239, in stop AttributeError: GuestAgent instance has no attribute '_sock' Thread-642::DEBUG::2014-03-25 15:46:55,024::BindingXMLRPC::913::vds::(wrapper) client [10.34.63.76]::call vmGetStats with ('2237e47b-4b9b-4efb-a18b-0234ab15d22b',) {} Version-Release number of selected component (if applicable): vdsm-4.10.2-30.1.el6ev.x86_64 How reproducible: 100% Steps to Reproduce: 1. 3.3 host and 3.2 host (see versions above) 2. have a VM on 3.3 host and migrate it to 3.2 host 3. shutdown/poweroff the VM on 3.2 host Actual results: not down, the VM is in Non Responding state Expected results: should work Additional info: