Redis instance is not running

The Redis pods appear to be in Init:CrashLoopBackOff after a cluster reboot or a possible network flux. Red Hat® OpenShift® Container Platform provides a method to restart when pods are in crashloop using the restart_redis serviceability action.


During a cluster reboot or possible network flux in the Red Hat OpenShift Container Platform environment, the Redis pods experience a deadlock and are unable to determine a leader pod. The pods appear with an Init:CrashLoopBackOff error.

Resolving the problem

Run the reset_redis serviceability action. For more information about the reset_redis serviceability action, see Restarting Redis.