The Redis service remains blocked in Stopped state in controller node

Issue

After controller-2 rebooted, cluster service redis is not able to start. Last log from redis is SIGTERM scheduling shutdown...

• /var/log/redis/redis.log

  93669:signal-handler (1576504751) Received SIGTERM scheduling shutdown...
  93669:M 16 Dec 14:59:11.447 # User requested shutdown...
  93669:M 16 Dec 14:59:11.447 * Saving the final RDB snapshot before exiting.
  93669:M 16 Dec 14:59:11.455 * DB saved on disk
  93669:M 16 Dec 14:59:11.455 * Removing the unix socket file.
  93669:M 16 Dec 14:59:11.456 # Redis is now ready to exit, bye bye...
  

• Cluster status

  pcs status
  
  Cluster name: tripleo_cluster
  Stack: corosync
  Current DC: ctr1- (version 1.1.18-11.el7_5.3-2b07d5c5a9) - partition with         
  quorum
  Last updated: Fri Feb 14 16:54:46 2020
  Last change: Fri Feb 14 15:55:47 2020 by root via crm_resource on ctr2-
  
  3 nodes configured
  23 resources configured
  
  Online: [ ctr0- ctr1- ctr2- ]
  
  Full list of resources:
  
   ip- (ocf::heartbeat:IPaddr2):       Started ctr1-
   Clone Set: haproxy-clone [haproxy]
   Started: [ ctr0- ctr1- ctr2- ]
   Master/Slave Set: galera-master [galera]
   Masters: [ ctr0- ctr1- ctr2- ]
   ip-xxx.xxx.83.250      (ocf::heartbeat:IPaddr2):       Started ctr0-
   ip-xxx.xxx..81.250      (ocf::heartbeat:IPaddr2):       Started ctr1-
   ip-xxx.xxx.81.251      (ocf::heartbeat:IPaddr2):       Started ctr0-
  Clone Set: rabbitmq-clone [rabbitmq]
   Started: [ ctr0- ctr1- ctr2- ]
   ip-xxx.xxx.82.250      (ocf::heartbeat:IPaddr2):       Started ctr1-
  Master/Slave Set: redis-master [redis]
  Masters: [ ctr1- ]
  Slaves: [ ctr0- ]
  Stopped: [ ctr2- ]