swift-bench throws container error when use_proxy = no

[Craig Cutforth]

I have a swift cluster with the account-server and container-server running on my proxy. When I run swift-bench with use_proxy=no to talk directly to the object-server, everything goes fine during the write and read phase. During the delete phase, however, swift-bench throws 400 errors because it is trying to delete the containers. Since I am writing directly to the object-server, the containers were not created.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/28622

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/28622
Committed: http://github.com/openstack/swift/commit/5f295d032933d035b973f8f1f0a90f47b249d571
Submitter: Jenkins
Branch: master

commit 5f295d032933d035b973f8f1f0a90f47b249d571
Author: Darrell Bishop <email address hidden>
Date: Wed May 8 14:43:56 2013 -0700

    Don't delete containers when they weren't created.

    When swift-bench is run in direct mode, don't try to delete the
    containers which weren't created.

    Fixes bug 1177960.

    Change-Id: Ice07e8729bb776e2b215894cf95fb80b64167a8d