Comment 1 for bug 2063367

I'm confused -- boto should only be talking to swift, which in turn will talk to keystone. When does boto talk to keystone?

Do you have some example (scrubbed) logs demonstrating the problem? Probably want separate logs for the client, swift proxy, and keystone.

Currently, the only way to configure the boto tests to skip would be to remove the s3_access_key*/s3_secret_key* configs, which would also cause the boto3 tests to skip. Especially given the age of the boto library, I think we'd be amenable to a patch that would make it an optional test dependency, though, and skip tests if it's not installed.