-
Task
-
Resolution: Done
-
Major
-
None
-
2.12.0 GA
-
3
-
False
-
None
-
False
-
Not Started
-
Not Started
-
Not Started
-
Not Started
-
Not Started
-
Not Started
-
Yes
-
API CCS Sprint 32 (3Scale), API CCS Sprint 33 (3Scale), API CCS Sprint 34 (3Scale), API CCS Sprint 35 (3Scale), API CCS Sprint 36 (3Scale)
Current behaviour
When performing an upgrade from 2.11 to 2.12 the documentation states that only Postgres 13 is supported when using an external DB. There is no possibility to remain in a supported configuration when performing the upgrade due to this limitation and in the event of a failed upgrade the unsupported configuration may not be able to be rolled back.
Expected behaviour
When Postgres is used as an external database for system then both versions 10 & 13 are supported to facilitate the upgrade procedure and provide some safety in the event of a failed upgrade of 3scale (the external DB might now be "stuck" on Postgres 13 until a successful upgrade of 3scale can be complete.
Regarding the external DB this is only relevant for the system DB, it is not expected to cover scenarios where the zync-db has also been externalised.
- is related to
-
THREESCALE-8862 Support MySQL 5.7 to allow for upgrades to remain in a supported configuration
- Closed
-
THREESCALE-8786 Clarify 3scale side procedures when using an external DB and updating the external DB
- Closed
- relates to
-
THREESCALE-8862 Support MySQL 5.7 to allow for upgrades to remain in a supported configuration
- Closed