Comment 2 for bug 1249727

> So we have a testsuite in 2 distinct parts

There are actually *three* parts:

* Unit tests, which don't require swift to be running, but which *do* require some level of installation -- in particular, our unit tests include some validation that entrypoints have been properly configured
* Functional tests, which require a functional swift (or swift-like) endpoint, defined in /etc/swift/test.conf
* Probe tests, which require a local swift instance that looks more-or-less like the documented Swift-All-In-One [1] -- this allows us to test a cluster during various failure scenarios

Looking at the unit tests reported:

* The "Unable to read test config /etc/swift/test.conf - file not found" message is awkward but benign -- the unit tests will still run whether that file's present or not. I'm really questioning the wisdom having unit tests that take config [2], though.

* The locale test should be fixed [3].

* The DistributionNotFound errors are legit; swift requires xattr, and plumbing in pkg_resources will enforce that.

* The test_get_logger_sysloghandler_plumbing failure is fixed [4].

[1] https://docs.openstack.org/swift/latest/development_saio.html
[2] As was introduced in https://github.com/openstack/swift/commit/f7fdb9c
[3] https://github.com/openstack/swift/commit/62b87fc
[4] Most likely in https://github.com/openstack/swift/commit/64756f8