Swift proxy gives 503 even though swift playbooks are executed

[SHASHANK TAVILDAR]

This is for AIO and multinode deployment using stable/newton branch

Steps I used to deploy swift:
1. Create partitions and label them as KOLLA_SWIFT_DATA.
2. Create Object, Container and Account rings for partitions labeled as KOLLA_SWIFT_DATA.
3. My /etc/kolla/swift/config has the required rings and .gz files.
4. All Kolla playbooks passed successfully.

Validate swift:
-> swift stat
RESP STATUS: 503 Service Unavailable

Proxy container logs: (AIO)
-> docker logs swift-proxy-server
swift-proxy-server: Account HEAD returning 503 for [] (txn: tx119e5ab980d04a4baebe8-00582df536) (client_ip: 192.168.0.233)
swift-proxy-server: ERROR with Account server 127.0.0.1:6001/dq1 re: Trying to HEAD /v1/AUTH_2853d92119b34324a9f06819b4b2d62a: Connection refused (txn: tx22674890a7af4f22812cd-00582df537) (client_ip: 192.168.0.233)
swift-proxy-server: ERROR with Account server 127.0.0.1:6001/vdf1 re: Trying to HEAD /v1/AUTH_2853d92119b34324a9f06819b4b2d62a: Connection refused (txn: tx22674890a7af4f22812cd-00582df537) (client_ip: 192.168.0.233)
swift-proxy-server: ERROR with Account server 127.0.0.1:6001/vdb1 re: Trying to HEAD /v1/AUTH_2853d92119b34324a9f06819b4b2d62a: Connection refused (txn: tx22674890a7af4f22812cd-00582df537) (client_ip: 192.168.0.233)

Request all to look at this issue and post your thoughts here.

[Paul Bourke (pauldbourke)]

Can you check are any containers stuck in 'restarting' mode? Unfortunately the playbooks wont detect this currently

[SHASHANK TAVILDAR (shasha.tavil)]

The containers are running and active. No containers in restarting/exit mode.

[David Rabel (rabel-b1)]

Is there a workaround for this?

[Jeffrey Zhang (jeffrey4l)]

This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.

If you can reproduce the bug, please:
* reopen the bug report (set to status "New")
* AND add the detailed steps to reproduce the issue (if applicable)
* AND leave a comment "CONFIRMED FOR: <RELEASE_NAME>"
  Only still supported release names are valid (OCATA, PIKE, QUEENS, ROCKY, ROCKY).
  Valid example: CONFIRMED FOR: OCATA