-
Bug
-
Resolution: Done
-
Major
-
2.8 GA
-
False
-
False
-
Not Started
-
Not Started
-
Not Started
-
Not Started
-
Not Started
-
Not Started
-
undefined
-
- Deploy 3scale version 2.7 via the operator
- Perform the migration from 2.7 to 2.8 using the operator
- _oc rsh dc/system-app _
- Run env | grep AMP_RELEASE
-
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.
- is caused by
-
THREESCALE-6209 Incorrect version number on 3scale
- Closed
-
THREESCALE-405 After migration from 2.0 to 2.1 version on 3scale Admin page is CR1
- Closed
-
THREESCALE-477 Version is not shown in the admin portal footer
- Closed
-
THREESCALE-1748 Documentation fix for upgrade 2.3 to 2.4 - memcached image and AMP_RELEASE variable
- Closed
-
THREESCALE-2538 2.5 system-oracle image build is still referring to AMP_RELEASE 2.4
- Closed
-
THREESCALE-5647 3scale version is not updated in Admin portal
- Closed
-
THREESCALE-122 GA AMP_RELEASE reports as CR
- Closed
- is related to
-
THREESCALE-7481 System exposes 3scale deployment metadata
- Closed
-
THREESCALE-6209 Incorrect version number on 3scale
- Closed
- relates to
-
THREESCALE-8047 AMP_RELEASE env variable not updated on Operator based Upgrade
- Closed
- links to