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

When migrating 3scale via the opeartor, AMP_RELEASE version does not get update

    XMLWordPrintable

Details

    • False
    • False
    • Not Started
    • Not Started
    • Not Started
    • Not Started
    • Not Started
    • Not Started
    • undefined
      1. Deploy 3scale version 2.7 via the operator
      2. Perform the migration from 2.7 to 2.8 using the operator
      3. _oc rsh dc/system-app _
      4. Run env | grep AMP_RELEASE

    Description

      When migrating 3scale using the 3scale operator the AMP_RELEASE version in system-environment confimap does not get update.

      I have noticed that AMP_RELEASE environment value only gets read here
      Note that the value displayed in the admin-console is read like this

      My questions:

      • Is this AMP_RELEASE value used for any other context/operation ?
      • Can we fix the operator to update the value of AMP_RELEASE, when migrating from one version to another?

       

      Dev notes:

      • "AMP_RELEASE" info will be removed from the env var list and also from the configmap as it is not being used.

      Attachments

        Issue Links

          is caused by

          Bug - A problem that impairs or prevents the functions of the product. THREESCALE-6209 Incorrect version number on 3scale

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. THREESCALE-405 After migration from 2.0 to 2.1 version on 3scale Admin page is CR1

          • 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

          Bug - A problem that impairs or prevents the functions of the product. THREESCALE-477 Version is not shown in the admin portal footer

          • 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

          Bug - A problem that impairs or prevents the functions of the product. THREESCALE-1748 Documentation fix for upgrade 2.3 to 2.4 - memcached image and AMP_RELEASE variable

          • 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

          Bug - A problem that impairs or prevents the functions of the product. THREESCALE-2538 2.5 system-oracle image build is still referring to AMP_RELEASE 2.4

          • 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

          Bug - A problem that impairs or prevents the functions of the product. THREESCALE-5647 3scale version is not updated in Admin portal

          • 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-122 GA AMP_RELEASE reports as CR

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Closed
          is related to

          Feature Request - Feature requests from customers and/or users THREESCALE-7481 System exposes 3scale deployment metadata

          • 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

          Bug - A problem that impairs or prevents the functions of the product. THREESCALE-6209 Incorrect version number on 3scale

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed
          relates to

          Bug - A problem that impairs or prevents the functions of the product. THREESCALE-8047 AMP_RELEASE env variable not updated on Operator based Upgrade

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Closed
          links to

          GitHub 3scale/3scale-operator#654: Remove AMP_RELEASE system env var

          Activity

            People

              Unassigned Unassigned
              rhn-support-cabeywar Chamal Abeywardhana
              Miroslav Jaroš Miroslav Jaroš
              Eguzki Astiz Lezaun Eguzki Astiz Lezaun
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: