This is still an issue and from what I can tell a specific change wasn't merged against this bug, so re-opening since I couldn't find it via LP search before (since it was Fix Committed):
http://logs.openstack.org/93/156693/7/check/check-tempest-dsvm-postgres-full/d3b26e8/logs/screen-n-cpu.txt.gz#_2015-03-12_16_38_17_567
http://logstash.openstack.org/#eyJzZWFyY2giOiJtZXNzYWdlOlwiX2RldGFjaF92b2x1bWVcIiBBTkQgbWVzc2FnZTpcImNhblxcJ3QgYmUgZGVjb2RlZFwiIEFORCB0YWdzOlwic2NyZWVuLW4tY3B1LnR4dFwiIiwiZmllbGRzIjpbXSwib2Zmc2V0IjowLCJ0aW1lZnJhbWUiOiI2MDQ4MDAiLCJncmFwaG1vZGUiOiJjb3VudCIsInRpbWUiOnsidXNlcl9pbnRlcnZhbCI6MH0sInN0YW1wIjoxNDI2MjYyNTc2ODI4LCJtb2RlIjoiIiwiYW5hbHl6ZV9maWVsZCI6IiJ9
This is still an issue and from what I can tell a specific change wasn't merged against this bug, so re-opening since I couldn't find it via LP search before (since it was Fix Committed):
http:// logs.openstack. org/93/ 156693/ 7/check/ check-tempest- dsvm-postgres- full/d3b26e8/ logs/screen- n-cpu.txt. gz#_2015- 03-12_16_ 38_17_567
http:// logstash. openstack. org/#eyJzZWFyY2 giOiJtZXNzYWdlO lwiX2RldGFjaF92 b2x1bWVcIiBBTkQ gbWVzc2FnZTpcIm NhblxcJ3QgYmUgZ GVjb2RlZFwiIEFO RCB0YWdzOlwic2N yZWVuLW4tY3B1Ln R4dFwiIiwiZmllb GRzIjpbXSwib2Zm c2V0IjowLCJ0aW1 lZnJhbWUiOiI2MD Q4MDAiLCJncmFwa G1vZGUiOiJjb3Vu dCIsInRpbWUiOns idXNlcl9pbnRlcn ZhbCI6MH0sInN0Y W1wIjoxNDI2MjYy NTc2ODI4LCJtb2R lIjoiIiwiYW5hbH l6ZV9maWVsZCI6I iJ9