Details
-
Bug
-
Resolution: Done
-
Major
-
None
-
2.4 GA
-
Not Started
-
Not Started
-
Not Started
-
Not Started
-
Not Started
-
Not Started
-
+
Description
When configuring Redis HA outside OpenShift for 3scale backend components according to the steps provided in the documentation (KCS), backend-worker and backend-cron deployments don't start. However backend-listener deployment starts successfully and redis data can be checked.
An example of the configuration of the environment variables to reproduce the issue is:
REDIS_QUEUES_SENTINEL_HOSTS: <IP1>:26379,<IP2>:26379,<IP3>:26379 REDIS_QUEUES_SENTINEL_ROLE: master REDIS_QUEUES_URL: redis://mymaster/1 REDIS_STORAGE_SENTINEL_HOSTS: <IP1>:26379,<IP2>:26379,<IP3>:26379 REDIS_STORAGE_SENTINEL_ROLE: master REDIS_STORAGE_URL: redis://mymaster/0
Where "mymaster" is the Sentinel group name.