Redis pods fail to start

Redis pods might fail to start after you run a backup and restore on Db2 Data Management Console.

Resolving the problem

To resolve the problem, complete the following steps:
  1. Check the status of the redis pods. Run the following command:
    oc get pod -l app.kubernetes.io/component=ibm-redis-cp -n {cpd-instance-namespace} | grep -Ev '1/1|2/2' 
    NAME                                                        READY   STATUS                  RESTARTS           AGE
ibm-dmc-1691575249974726-rediscp-haproxy-6dc5bccf9c-r98rl   0/1     Running                 1267 (106s ago)    3d22h
ibm-dmc-1691575249974726-rediscp-server-0                   0/2     Init:CrashLoopBackOff   1029 (39s ago)     3d22h
ibm-dmc-1691575249974726-rediscp-server-2                   0/2     Init:CrashLoopBackOff   1029 (2m34s ago)   3d22h
  2. Delete all the redis pods. For example:
    oc delete pod ibm-dmc-1691575249974726-rediscp-haproxy-6dc5bccf9c-r98r ibm-dmc-1691575249974726-rediscp-server-0 ibm-dmc-1691575249974726-rediscp-server-2 -n {cpd-instance-namespace}
  3. Wait for all the redis pods to restart and check the status again. Run the following command:
    oc get pod -l app.kubernetes.io/component=ibm-redis-cp -n {cpd-instance-namespace} 
    NAME                                                        READY   STATUS    RESTARTS   AGE
ibm-dmc-1691575249974726-rediscp-haproxy-6dc5bccf9c-9flh2   1/1     Running   0          3d22h
ibm-dmc-1691575249974726-rediscp-server-0                   2/2     Running   0          3d22h
ibm-dmc-1691575249974726-rediscp-server-1                   2/2     Running   0          2d16h
ibm-dmc-1691575249974726-rediscp-server-2                   2/2     Running   0          3d22h