Bug 918209
| Summary: | vdsm: Migration is failing due to thread collision (race) | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Elad <ebenahar> | ||||||||
| Component: | vdsm | Assignee: | Saveliev Peter <peet> | ||||||||
| Status: | CLOSED WORKSFORME | QA Contact: | Elad <ebenahar> | ||||||||
| Severity: | high | Docs Contact: | |||||||||
| Priority: | unspecified | ||||||||||
| Version: | 3.2.0 | CC: | abaron, bazulay, dron, hateya, iheim, lpeer, michal.skrivanek, sgrinber, ykaul | ||||||||
| Target Milestone: | --- | Keywords: | Regression | ||||||||
| Target Release: | 3.2.0 | Flags: | peet:
needinfo+
sgrinber: Triaged+ |
||||||||
| Hardware: | x86_64 | ||||||||||
| OS: | Unspecified | ||||||||||
| Whiteboard: | virt | ||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2013-04-03 13:50:02 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: |
|
||||||||||
Version-Release number of selected component (if applicable): vdsm-4.10.2-10.0.el6ev.x86_64 Version-Release number of selected component (if applicable): vdsm-4.10.2-10.0.el6ev.x86_64 missing libvirt log there are multiple errors in vdsm log, which one you mean by "once" - when? Created attachment 705869 [details]
libvirt.log
(In reply to comment #5) > Created attachment 705869 [details] > libvirt.log this is from a different day and/or a wrong log. I need to know which error you are referring to moving to beta2 until it's clarified this is a real issue or not. Need to get time of the failure and all of engine, vdsm, libvirt and qemu logs Created attachment 706273 [details]
libvirt logs
Elad, can you point me to the exact timestamp of the case? I see several qemu crashes in logs, but no one that can be interpreted as a bug description. Closing the bug for now because of reproduction difficulty issue. Will reopen as soon as we will manage to reproduce. |
Created attachment 705552 [details] logs Description of problem: When perfoming migration, the destination VDSM is collecting statistics of the migrated VM while lidvirt has not cmplete the creation of the VM, which causing to a race. Version-Release number of selected component (if applicable): How reproducible: happened to me once Steps to Reproduce: 1. migrate a VM Actual results: The migration don't work Expected results: The migration should work Additional info: see logs attatched