Uploaded image for project: 'Red Hat 3scale API Management'
  1. Red Hat 3scale API Management
  2. THREESCALE-8728

Support Postgres 10.x to allow for upgrades to remain in a supported configuration

    XMLWordPrintable

Details

    • Task
    • Resolution: Done
    • Major
    • None
    • 2.12.0 GA
    • Tests
    • 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)

    Description

      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.

      Attachments

        Issue Links

          is related to

          Task - Represents a small unit of work that is not end-user facing. THREESCALE-8862 Support MySQL 5.7 to allow for upgrades to remain in a supported configuration

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) THREESCALE-8786 Clarify 3scale side procedures when using an external DB and updating the external DB

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • To Document
          relates to

          Task - Represents a small unit of work that is not end-user facing. THREESCALE-8862 Support MySQL 5.7 to allow for upgrades to remain in a supported configuration

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              Unassigned Unassigned
              rhn-support-keprice Kevin Price
              Darren Fennessy Darren Fennessy
              Filip Čáp Filip Čáp
              Kevin Price Kevin Price
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: