At an initial glance at the bug description, I think there is a problem with the logs you've shown us. I'm not saying there isn't a bug here. Looks like clay have managed to recreate it. However in the 2.5 snippet of logs, you show a bunch of connection timeouts when hitting object servers for:
GET /v1/AUTH_ECTesting/EC10-2-1/objects-0-56-24
But the example 404 proxy response is for:
GET /v1/AUTH_ECTesting/EC10-2-1/objects-0-67-22
So for a different object, which may actually not exist. (although maybe they do and this is also caused by the timeout).
At an initial glance at the bug description, I think there is a problem with the logs you've shown us. I'm not saying there isn't a bug here. Looks like clay have managed to recreate it. However in the 2.5 snippet of logs, you show a bunch of connection timeouts when hitting object servers for:
GET /v1/AUTH_ ECTesting/ EC10-2- 1/objects- 0-56-24
But the example 404 proxy response is for:
GET /v1/AUTH_ ECTesting/ EC10-2- 1/objects- 0-67-22
So for a different object, which may actually not exist. (although maybe they do and this is also caused by the timeout).