yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #11626
[Bug 1053364] Re: Add SIGPIPE handler to subprocess execution in rootwrap and utils.execute
** No longer affects: cinder (Ubuntu)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1053364
Title:
Add SIGPIPE handler to subprocess execution in rootwrap and
utils.execute
Status in Cinder:
Fix Released
Status in Cinder folsom series:
Fix Released
Status in OpenStack Neutron (virtual network service):
Fix Released
Status in neutron folsom series:
Fix Released
Status in OpenStack Compute (Nova):
Fix Released
Status in OpenStack Compute (nova) folsom series:
Fix Released
Status in “nova” package in Ubuntu:
Fix Committed
Status in “quantum” package in Ubuntu:
Fix Released
Status in “cinder” source package in Quantal:
Fix Released
Status in “nova” source package in Quantal:
Fix Released
Status in “quantum” source package in Quantal:
Fix Released
Bug description:
As explained here:
http://www.chiark.greenend.org.uk/ucgi/~cjwatson/blosxom/2009-07-02
-python-sigpipe.html
Python ignores SIGPIPE on startup, because it prefers to check every
write and raise an IOError exception rather than taking the signal.
This is all well and good for Python itself, but most Unix
subprocesses don't expect to work this way. Thus, when you are
creating subprocesses from Python, it is very important to set SIGPIPE
back to the default action. Before I realised this was necessary, I
wrote code that caused serious data loss due to a child process
carrying on out of control after its parent process died!
Our execution stuff should make use of that.
To manage notifications about this bug go to:
https://bugs.launchpad.net/cinder/+bug/1053364/+subscriptions