Lifecycle Agent Operator version 4.18 is incorrectly installed on OpenShift 4.17 or older clusters

Solution Verified - Updated

Environment

  • Red Hat OpenShift Container Platform (RHOCP)
    - < 4.18
  • Lifecycle Agent Operator 4.18

Issue

After a catalog update, the Lifecycle Agent Operator may have been upgraded to version 4.18, which is not supported on OpenShift Container Platform (OCP) versions 4.17 or older clusters.

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

Resolution

1. Preconditions & Safety Checks

Before initiating the removal or installation process, the following conditions must be met:

  • No Active Operations: Verify that no IBU (Image Based Upgrades) are currently in progress.
  • Backup Policy: Confirmed that no backup is required for LCA (Lifecycle Agent).

2. Clean Uninstallation (CLI Commands)

To completely remove the operator and its metadata, execute the following commands in sequence:

  1. Check the current version of the Subscription, CSV and Installplan:
$ oc get subscription -n openshift-lifecycle-agent
$ oc get csv -n openshift-lifecycle-agent
$ oc get installplan -n openshift-lifecycle-agent
  1. Delete the Subscription:
$ oc delete subscriptions.operators.coreos.com -n openshift-lifecycle-agent <subscription_name>
subscription.operators.coreos.com "<subscription_name>" deleted from openshift-lifecycle-agent namespace
  1. Delete the Cluster Service Version (CSV):
    Replace with the specific v4.18 string found in step 1.
$ oc delete csv -n openshift-lifecycle-agent lifecycle-agent.v<version>
clusterserviceversion.operators.coreos.com "lifecycle-agent.v<version>" deleted from openshift-lifecycle-agent namespace
  1. Delete Installplan:
$ oc delete installplan <installplan_name> -n openshift-lifecycle-agent
installplans.operators.coreos.com "<installplan_name>" deleted from openshift-lifecycle-agent namespace
  1. Remove Custom Resource Definitions (CRDs):
    Note: Only remove CRDs if a fresh state is required for the new installation.
$ oc get crd | grep lca
imagebasedupgrades.lca.openshift.io                               2026-02-18T19:52:30Z
seedgenerators.lca.openshift.io                                   2026-02-18T19:52:30Z

$ oc delete crd imagebasedupgrades.lca.openshift.io seedgenerators.lca.openshift.io
customresourcedefinition.apiextensions.k8s.io "imagebasedupgrades.lca.openshift.io" deleted
customresourcedefinition.apiextensions.k8s.io "seedgenerators.lca.openshift.io" deleted

3. Targeted Reinstallation

To reinstall and pin the operator to the desired version, create the Subscription manifest.
Subscription Manifest (lca-subscription.yaml)

apiVersion: operators.coreos.com/v1alpha1
kind: Subscription
metadata:
  name: lifecycle-agent
  namespace: openshift-lifecycle-agent
spec:
  channel: "stable" 
  name: lifecycle-agent
  source: redhat-operators
  sourceNamespace: openshift-marketplace
  installPlanApproval: Manual

Apply the Installation:

  1. Create the subscription:
$ oc apply -f lca-subscription.yaml
subscription.operators.coreos.com/lifecycle-agent created
  1. Approve the InstallPlan:
    Since installPlanApproval is set to Manual, you must retrieve and approve the plan:
$ oc get installplans.operators.coreos.com -n openshift-lifecycle-agent
NAME            CSV                       APPROVAL   APPROVED
install-vgp8f   lifecycle-agent.v4.16.5   Manual     false

$ oc patch installplan install-vgp8f -n openshift-lifecycle-agent --type merge --patch '{"spec":{"approved":true}}' '{"spec":{"approved":true}}'
installplan.operators.coreos.com/install-vgp8f patched

4. Post-Installation Validation

Verify Operator Status:

$ oc get csv -n openshift-lifecycle-agent
NAME                      DISPLAY           VERSION   REPLACES                  PHASE
lifecycle-agent.v4.16.5   Lifecycle Agent   4.16.5    lifecycle-agent.v4.16.4   Succeeded

Verify Pods:

$ oc get pods -n openshift-lifecycle-agent | grep lifecycle-agent
lifecycle-agent-controller-manager-5c654794f9-mrlpf   2/2     Running   0          45s

Root Cause

For several hours on February 3, 2026, Red Hat released 4.18 Red Hat Operators catalog content into 4.12-4.17 clusters.

For more information, including Diagnostic Steps, please refer to Red Hat Operator has version higher than the cluster version.

Diagnostic Steps

For more information, including Diagnostic Steps, please refer to Red Hat Operator has version higher than the cluster version.

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.