Comment 10 for bug 1229475

After some more looking at the run dims linked in comment #9, it's clear that the error comes from neutronclient getting a bogus fd. That fd (16) is actively in use by rpc. neutronclient barfs on it because it ends up reading data from rabbitmq.

http://logs.openstack.org/11/49011/4/check/check-tempest-devstack-vm-neutron/0ab22df/logs/screen-n-cpu.txt.gz#_2013-10-01_12_34_23_604