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

AMP_RELEASE env variable not updated on Operator based Upgrade

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Minor Minor
    • None
    • 2.11.1 GA
    • 3scale Operator
    • False
    • False
    • Not Started
    • Not Started
    • Not Started
    • Not Started
    • Not Started
    • Not Started

      AMP_RELEASE is not upgraded from 2.10 to 2.11 on an Operator Upgrade

      After upgrade,

      $ oc rsh -c system-master dc/system-app /bin/bash -c "env | grep AMP_RELEASE"
      AMP_RELEASE=2.10

      It is set correctly to 2.11 on a fresh install of 3scale.

      If this is used to determine if 3scale upgrade is successful, this can be misleading. 3scale docs do describe the new annotation values to determine if 3scale upgrade has been successful. However, this may be missed and AMP_RELEASE checked instead.  

       

              Unassigned Unassigned
              rhn-support-cvajjhal Chandrasekhar Vajjhala (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: