yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #14920
[Bug 1282206] Re: Uncaught GreenletExit in ProcessLauncher if wait called after greenlet kill
Was this synced to trunk in Juno?
** Also affects: nova/icehouse
Importance: Undecided
Status: New
** Changed in: nova
Importance: Undecided => High
** Changed in: nova/icehouse
Importance: Undecided => High
** Changed in: nova/icehouse
Assignee: (unassigned) => Matt Riedemann (mriedem)
** Changed in: nova/icehouse
Status: New => In Progress
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1282206
Title:
Uncaught GreenletExit in ProcessLauncher if wait called after greenlet
kill
Status in OpenStack Neutron (virtual network service):
New
Status in OpenStack Compute (Nova):
In Progress
Status in OpenStack Compute (nova) icehouse series:
In Progress
Status in Oslo - a Library of Common OpenStack Code:
Fix Released
Bug description:
I'm running wait in ProcessLauncher in a green thread. I attempted to
kill the green thread and then call wait so that the process launcher
object can reap its child processes cleanly. This resulted in a trace
resulting from a GreenletExit exception being thrown.
The eventlet documentation states multiple times that GreenletExit is
thrown after .kill() has been called to kill a thread. I think
ProcessLauncher should expect this and deal with it.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1282206/+subscriptions
References