The errors are reproduced because the haproxy settings are not correct after setting ha_proxy to yes in globals.yml.
Here is and example of the error log:
2023-07-26T12:06:51-06:00 syslog.local0.err {"Payload":"swift-proxy-server: ERROR with Container server <HAPROXY_PROXY_SERVER_IP>:6002/d0 re: Trying to HEAD /v1/AUTH_96d55c41d2094f679c37078b034f552e/piwik-backup: Connection refused (txn: tx1fcdbfc1d82d40d38f92f-0064c160bb)\u0000","log_level":"err","Hostname":"<HOSTNAME>","programname":"swift"}
My description in the original post is clear. There are no services cfg files created for swift object, container, and account servers thus when there is a call to <HAPROXY_PROXY_SERVER_IP>:6002, which apparently occurs when accessing through horizon, the connection refused is refused. When the cfg files are created, the issue is resolved.
The errors are reproduced because the haproxy settings are not correct after setting ha_proxy to yes in globals.yml.
Here is and example of the error log:
2023-07- 26T12:06: 51-06:00 syslog.local0.err {"Payload" :"swift- proxy-server: ERROR with Container server <HAPROXY_ PROXY_SERVER_ IP>:6002/ d0 re: Trying to HEAD /v1/AUTH_ 96d55c41d2094f6 79c37078b034f55 2e/piwik- backup: Connection refused (txn: tx1fcdbfc1d82d4 0d38f92f- 0064c160bb) \u0000" ,"log_level" :"err", "Hostname" :"<HOSTNAME> ","programname" :"swift" }
My description in the original post is clear. There are no services cfg files created for swift object, container, and account servers thus when there is a call to <HAPROXY_ PROXY_SERVER_ IP>:6002, which apparently occurs when accessing through horizon, the connection refused is refused. When the cfg files are created, the issue is resolved.