Comment 11 for bug 1540531

Trying the install and teardown with Kilo after doing a Liberty install and then checkout to Kilo seems to provoke the same behavior. The /var/log/swift/proxy-error.log file is being created and filled and the Kilo AIO install fails.

With logging disabled, the logs are still being filled.

Example log traffic:

Mar 23 15:13:00 localhost haproxy[17620]: backend repo_all-back has no server available!
Mar 23 15:13:01 localhost haproxy[17620]: Server swift_proxy-back/aio1_swift_proxy_container-8871439c is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
Mar 23 15:13:01 localhost haproxy[17620]: backend swift_proxy-back has no server available!
Mar 23 15:22:00 localhost haproxy[17620]: Server repo_all-back/aio1_repo_container-2cb95cdd is UP, reason: Layer4 check passed, check duration: 0ms. 1 active and 0 backup servers online. 0 sessions requeued, 0 total in queue.