Dapr Sidecar fails to reconnect to rabbitmq cluster defined as pubsub component

[sleom]

Expected Behavior

The Dapr publisher should automatically reconnect to the remaining nodes in the RabbitMQ cluster after one node goes down, allowing messages to be published without manual intervention.

Actual Behavior

When a node in the RabbitMQ cluster becomes unavailable:
The Dapr publisher fails to reconnect, and publishing to RabbitMQ fails.
Errors are repeatedly logged, with messages indicating that the connection is not open.

Steps to Reproduce the Problem

publisher-pod.yaml.txt
component.yaml.txt

1. Set up a publisher application with a Dapr pub/sub publisher as a sidecar.
2. Configure the publisher component to use RabbitMQ service created by RabbitMQ cluster deployment on Kubernetes
3. Find the RabbitMQ node that the publisher is connected to
4. Take down/restart this node.
5. Observe the logs and error messages in the publisher.

Release Note

RELEASE NOTE:

[github-actions]

This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged (pinned, good first issue, help wanted or triaged/resolved) or other activity occurs. Thank you for your contributions.

[vadim-tychonoff]

still an issue

[github-actions]

This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged (pinned, good first issue, help wanted or triaged/resolved) or other activity occurs. Thank you for your contributions.

[sleom]

Why is it ignored?

[github-actions]

This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged (pinned, good first issue, help wanted or triaged/resolved) or other activity occurs. Thank you for your contributions.