Bug #2072461 “RabbitMQ Deployment via OpenStack-Helm Script Enco…” : Bugs : openstack-helm

[Issue]

The deployment script for OpenStack components such as RabbitMQ, Keystone etc. is failing.

[Issue Detail]

I executed the RabbitMQ deployment script from the OpenStack-Helm master branch, but the deployment failed with the following error:

https://github.com/openstack/openstack-helm/blob/master/tools/deployment/component/common/rabbitmq.sh

client.go:310: [debug] Starting delete for “rabbitmq-cluster-wait” Job
client.go:128: [debug] creating 1 resource(s)
client.go:540: [debug] Watching for changes to Job rabbitmq-cluster-wait with timeout of 10m0s
client.go:568: [debug] Add/Modify event for rabbitmq-cluster-wait: ADDED
client.go:607: [debug] rabbitmq-cluster-wait: Jobs active: 0, jobs failed: 0, jobs succeeded: 0
client.go:568: [debug] Add/Modify event for rabbitmq-cluster-wait: MODIFIED
client.go:607: [debug] rabbitmq-cluster-wait: Jobs active: 1, jobs failed: 0, jobs succeeded: 0
client.go:568: [debug] Add/Modify event for rabbitmq-cluster-wait: MODIFIED
client.go:607: [debug] rabbitmq-cluster-wait: Jobs active: 1, jobs failed: 0, jobs succeeded: 0
upgrade.go:434: [debug] warning: Upgrade “rabbitmq” failed: post-upgrade hooks failed: timed out waiting for the condition
Error: UPGRADE FAILED: post-upgrade hooks failed: timed out waiting for the condition
helm.go:84: [debug] post-upgrade hooks failed: timed out waiting for the condition
UPGRADE FAILED

Upon executing the deployment script, it creates the RabbitMQ pod “rabbitmq-cluster-wait-phbm7”. Although the pod is in a running state, the logs for this pod display the following message:

Traceback (most recent call last):
  File “/usr/local/bin/rabbitmqadmin”, line 613, in http
    conn.request(method, path, body, headers)
  File “/usr/lib/python3.10/http/client.py”, line 1283, in request
    self._send_request(method, url, body, headers, encode_chunked)
  File “/usr/lib/python3.10/http/client.py”, line 1329, in _send_request
    self.endheaders(body, encode_chunked=encode_chunked)
  File “/usr/lib/python3.10/http/client.py”, line 1278, in endheaders
    self._send_output(message_body, encode_chunked=encode_chunked)
  File “/usr/lib/python3.10/http/client.py”, line 1038, in _send_output
    self.send(msg)
  File “/usr/lib/python3.10/http/client.py”, line 976, in send
    self.connect()
  File “/usr/lib/python3.10/http/client.py”, line 942, in connect
    self.sock = self._create_connection(
  File “/usr/lib/python3.10/socket.py”, line 824, in create_connection
    for res in getaddrinfo(host, port, 0, SOCK_STREAM):
  File “/usr/lib/python3.10/socket.py”, line 955, in getaddrinfo
    for res in _socket.getaddrinfo(host, port, family, type, proto, flags):
  socket.gaierror: [Errno -3] Temporary failure in name resolution
  *** Could not connect: [Errno -3] Temporary failure in name resolution

Similarly, the deployments for Keystone and several other components are also failing. What could be the possible reasons for these deployment failures?