Details
-
Bug
-
Resolution: Duplicate
-
Minor
-
None
-
2.11.1 GA
-
False
-
False
-
Not Started
-
Not Started
-
Not Started
-
Not Started
-
Not Started
-
Not Started
Description
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.
Attachments
Issue Links
- is related to
-
THREESCALE-7427 When migrating 3scale via the opeartor, AMP_RELEASE version does not get update
- Closed