Redis failover causes Event-Driven Ansible activation failures

Updated -

Issue description

When a primary Redis node enters a 'failed' state and a new primary node is promoted, the Event-Driven Ansible workers and scheduler are unable to re-connect to the Redis cluster. This causes activations to fail until the containers or pods are recycled.

Use the procedures in this article to manually recycle the containers or pods.

IMPORTANT

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content