-
Bug
-
Resolution: Done
-
Blocker
-
2.5 CR2
-
5
-
Not Started
-
Not Started
-
Not Started
-
Not Started
-
Not Started
-
Not Started
-
- Have custom System and backend redis
- Deploy the HA template
- Set all required parameters
- It fails
-
3scale 2019-04-23
After `MESSAGE_BUS_REDIS_URL` was introduced, the HA template fails to deploy due to missing corresponding parameter.
In the past, system component used to inherit the connection string set for `REDIS_URL` and then changed the logical db to `/8`. This second connection was used for message bus. Now, if not specified, system assumes `redis://system-redis/8` as default[1], which is not a valid option in HA deployments. As a consequence, system-(app|sidekiq|sphinx) keeps crashing until `MESSAGE_BUS_REDIS_URL` env var is set.
We basically have 3 different options to address this issue:
- Document the workaround (i.e. how to manually set the missing env vars) and users will have to manually define a new env var to get the HA deploy profile working
This is pretty hacky and not nice, as people won't read the docs until it fails. - Change to HA template (and Operator HA deploy) requiring a new release of both, and some new testing.
We see long-term maintainability issues with this, and upgrade complexity, in Operator version in particular. - Code change to system to avoid the issue and a re-release and some re-testing of System by QE
Probably the best fix in terms of customer impact and longer-term maintainability.....but needs a new System release.