APIcast Operator inadvertently upgraded to version 2.16 on OCP 4.12-4.13 clusters

Solution Verified - Updated

Environment

  • Red Hat OpenShift Container Platform (RHOCP)
    • 4
  • Red Hat 3scale API Management On-premises
    • 2.16.0
    • 2.16.1
    • 2.16.2
  • Red Hat Integration - 3scale APIcast gateway Operator

Issue

After a catalog update, the APIcast Operator may have been upgraded to version v2.16, which is not supported on OpenShift Container Platform (OCP) versions 4.13 or older clusters.

This article covers the specific remediation for the APIcast Operator. For the general issue affecting multiple operators, refer to Red Hat Operator has version higher than the cluster version.

Resolution

Verify 3scale version

oc get APIManager -o json | jq -r ".items[].metadata.annotations"

Take note of "apps.3scale.net/apimanager-threescale-version"

Follow the below steps to recover the APIcast Operator:

  • Back up apicasts.apps.3scale.net Custom Resources from any namespaces the operator is installed.
  • Uninstall APIcast operator and APIcast Custom Resource Definition (CRD)
  • Re-install the APIcast operator with the version supported on your cluster
  • Re-create APIcast CR

Diagnostic Steps

Check to see if the incorrect CSV is installed

$ oc get csv -A | grep "Red Hat Integration - 3scale APIcast gateway"

3scale-test                            apicast-operator.v0.13.2   Red Hat Integration - 3scale APIcast gateway   0.13.2                      Succeeded

In this example from an OpenShift version 4.12 cluster, the CSV version is expected to be version v0.12.x or lower, but instead it is v0.13.x. In this case, the above remediation steps should be followed to downgrade APIcast operator.

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.