Windows Machine Config Operator inadvertently upgraded to version 10.18 on OCP versions below 4.18

Solution Verified - Updated

Environment

  • Red Hat OpenShift Container Platform (RHOCP)
    • 4
  • Windows Machine Config Operator
    • 10.18.0
    • 10.18.1

Issue

During the incident window (see Red Hat Operator has version higher than the cluster version), some clusters on OCP 4.12–4.17 received the 4.18 catalog content. Clusters with automatic install plan approval may have mistakenly upgraded the Windows Machine Config Operator to version v10.18, a version meant only for OCP 4.18 clusters.

Windows Machine Config Operator does not allow running on a cluster without the expected Kubernetes version.
WMCO v10.18 targets Kubernetes v1.31. This Kubernetes version is only used by OpenShift 4.18 clusters.

Because of this, the operator will enter CrashLoopBackOff, and be nonfunctional.

Resolution

Remediation for this issue is to uninstall the mistakenly installed version, and reinstalling the version appropriate for your cluster.
All operands will be unaffected, including Windows nodes.

  1. Uninstall the operator: https://docs.redhat.com/en/documentation/openshift_container_platform/4.17/html/operators/administrator-tasks#olm-deleting-operators-from-a-cluster

  2. Re-install the operator https://docs.redhat.com/en/documentation/openshift_container_platform/4.17/html/operators/administrator-tasks#olm-adding-operators-to-a-cluster

Product(s)
Components

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.