Loki operator does not start upgrade from version 5.4 to 5.7
Environment
- Red Hat OpenShift Container Platform (RHOCP)
- 4
- Red Hat OpenShift on AWS (ROSA)
- 4
- Red Hat OpenShift Dedicated (OSD)
- 4
- Red Hat OpenShift on Azure (ARO)
- 4
Issue
Lokioperator cannot be upgraded from version 5.4 to 5.7- The upgrade doesn't started after changing upgrade channel to the
stable-5.7 Lokioperator version 5.4 is blockingOpenShiftcluster upgrade, which would required to upgradeLokito higher version
Resolution
- If the current installed version of
Lokioperator is 5.4 then it cannot be upgraded directly to 5.7. The upgrade process needs to go as per following path5.4 -> 5.5 (stable 5.5) -> 5.6 (stable 5.6)-> 5.7 (stable 5.7) - Despite the
skip-versionupdate is possible thesequentialupgrade is recommended. - The
Lokioperator must be deployed to the global operator group namespaceopenshift-operators-redhat
Root Cause
Loki subscriptionis configured withstable-5.7and it is not supported to be upgraded directly from version 5.4
Diagnostic Steps
-
Log into cluster and check the
subscriptionand the current version of theLokioperator
Note: this can be done though theOCM Web UIas well.$ oc get subscription,installplan -n openshift-operators-redhat NAME PACKAGE SOURCE CHANNEL subscription.operators.coreos.com/loki-operator loki-operator redhat-operators stable-5.7 NAME CSV APPROVAL APPROVED installplan.operators.coreos.com/install-27s42 loki-operator.5.4.12 Automatic true installplan.operators.coreos.com/install-2wlsg loki-operator.5.4.14 Automatic true installplan.operators.coreos.com/install-cq7bc loki-operator.5.4.10 Automatic true installplan.operators.coreos.com/install-kw6z4 loki-operator.5.4.13 Automatic true installplan.operators.coreos.com/install-qrqsf loki-operator.5.4.11 Automatic true$ oc get subscription/loki-operator -o yaml -n openshift-operators-redhat | grep currentCSV currentCSV: loki-operator.5.4.14
-
The available starting version for particular
operator-indexcan be identified by usingopmcli which can be installed by following this solution$ opm alpha list bundles registry.redhat.io/redhat/redhat-operator-index:v4.11 loki-operator PACKAGE CHANNEL BUNDLE REPLACES SKIPS SKIP RANGE IMAGE loki-operator candidate loki-operator.5.4.14 >=5.4.0-0 <5.4.14 loki-operator stable loki-operator.v5.7.0 >=5.5.0-0 <5.7.0 loki-operator stable loki-operator.v5.7.1 loki-operator.v5.7.0 >=5.5.0-0 <5.7.1 loki-operator stable loki-operator.v5.7.2 loki-operator.v5.7.1 >=5.5.0-0 <5.7.2 loki-operator stable loki-operator.v5.7.3 loki-operator.v5.7.2 >=5.5.0-0 <5.7.3 loki-operator stable-5.5 loki-operator.5.5.13 >=5.4.0-0 <5.5.13 loki-operator stable-5.6 loki-operator.v5.6.1 >=5.4.0-0 <5.6.1 loki-operator stable-5.6 loki-operator.v5.6.2 loki-operator.v5.6.1 >=5.4.0-0 <5.6.2 loki-operator stable-5.6 loki-operator.v5.6.3 loki-operator.v5.6.2 >=5.4.0-0 <5.6.3 loki-operator stable-5.6 loki-operator.v5.6.4 loki-operator.v5.6.3 >=5.4.0-0 <5.6.4 loki-operator stable-5.6 loki-operator.v5.6.5 loki-operator.v5.6.4 >=5.4.0-0 <5.6.5 loki-operator stable-5.6 loki-operator.v5.6.6 loki-operator.v5.6.5 >=5.4.0-0 <5.6.6 loki-operator stable-5.6 loki-operator.v5.6.7 loki-operator.v5.6.6 >=5.4.0-0 <5.6.7 loki-operator stable-5.6 loki-operator.v5.6.8 loki-operator.v5.6.7 >=5.4.0-0 <5.6.8 loki-operator stable-5.7 loki-operator.v5.7.0 >=5.5.0-0 <5.7.0 <---starts from 5.5.0 loki-operator stable-5.7 loki-operator.v5.7.1 loki-operator.v5.7.0 >=5.5.0-0 <5.7.1 loki-operator stable-5.7 loki-operator.v5.7.2 loki-operator.v5.7.1 >=5.5.0-0 <5.7.2 loki-operator stable-5.7 loki-operator.v5.7.3 loki-operator.v5.7.2 >=5.5.0-0 <5.7.3
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.
Comments