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

Upgrade documentation is incomplete

    XMLWordPrintable

Details

    • Documentation for multi-step 2.x upgrade path
    • Not Started
    • Not Started
    • Not Started
    • Not Started
    • Not Started
    • Not Started
    • +
    • 100
    • 100% 100%

    Description

      Upgrading AMP from 2.1 up to 2.6 following the documentation is not easy.
      An AMP installation upgraded step by step up to 2.4 does not look enough like a clean 2.4 installation to simply follow the documented 2.5 and 2.6 upgrade to work.

      The resulting yml strongly differs from the clean one so the upgrade guide, without any integration, leads to errors.

      Attachments

        1. backend-cron.patch
          2 kB
        2. backend-worker.patch
          2 kB
        3. system-app-podcontainers.patch
          5 kB
        4. system-app-prehookpod-json.patch
          4 kB
        5. system-sidekiq.patch
          4 kB
        6. system-sphinx.patch
          1 kB
        7. upgrade-3scale.zip
          19 kB
        8. UpgradeProcedure.odt
          86 kB

        Issue Links

          causes

          Bug - A problem that impairs or prevents the functions of the product. THREESCALE-4204 Missing elements from backend-listener deploymentConfig

          • 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
          is caused by

          Task - Represents a small unit of work that is not end-user facing. THREESCALE-3634 Create documentation draft for 3scale upgrade 2.6 to 2.7 (templates and 3scale-operator)

          • 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
          is related to

          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-4898 UI warning + document that changing deployment_option causes Base URLs to be cleared

          • 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
          links to

          Web Link KCS

          Activity

            People

              Unassigned Unassigned
              rhn-support-cpalmier Carlo Palmieri (Inactive)
              Marian Ganisin Marian Ganisin (Inactive)
              Votes:
              1 Vote for this issue
              Watchers:
              14 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: