Created attachment 412105 [details]
parent process core
Description of problem:
After running multiple migrations from host A to host B one of the guests stuck at "Migration Destination" status forever.
After running "pgrep vdsm" command on the host i noticed that there are 3 vdsm processes instead of two.
According to email@example.com this issue happen due to python deadlock.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Created attachment 412107 [details]
child process core
To be more exact: following the backtrace of the child process hints that it was created by subprocess module. Before the expected exec(), garbage collection fired, and vdsm's task.Task.__del__ was called. The latter blocks deep inside logging module.
It might be a bug in one of the mentioned python modules, or that logging should not be used in __del__, or something completely different.
Please attach vdsm log.
Do you have a link to the .py code that's being executed?
http://bob.eng.lab/builds/sm64/vdsm22-4.5-54.el5rhev.x86_64.rpm should be pretty close.
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated in the
current release, Red Hat is unfortunately unable to address this
request at this time. Red Hat invites you to ask your support
representative to propose this request, if appropriate and relevant,
in the next release of Red Hat Enterprise Linux.
Development Management has reviewed and declined this request.
You may appeal this decision by reopening this request.
I don't mind this bug closure, as we are using https://pypi.python.org/pypi/cpopen for quite some time in order to avoid this issue (and others).