Uploaded image for project: 'Red Hat Workload Availability'
  1. Red Hat Workload Availability
  2. RHWA-389

[doc] Installation of self node remediation operator using the CLI is missing the starting version in subscription

XMLWordPrintable

    • False
    • Hide

      None

      Show
      None
    • False
    • Moderate

      In the actual version of documentation version 12.8, section "2.4. Installing the Self Node Remediation Operator by using the CLI " [1],

      the following example for a subscription is mentioned:

      apiVersion: operators.coreos.com/v1alpha1
      kind: Subscription
      metadata:
          name: self-node-remediation-operator
          namespace: self-node-remediation 
      spec:
          channel: stable
          installPlanApproval: Manual 
          name: self-node-remediation-operator
          source: redhat-operators
          sourceNamespace: openshift-marketplace
          package: self-node-remediation

      However, when applying it, the conditions reflect that it cannot judge about the version to use since it has different versions available in the package:

      [root@ocp68-jump snro-install]# oc get sub/self-node-remediation -o yaml |grep -A25 conditions:
        conditions:
        - lastTransitionTime: "2025-10-29T14:41:11Z"
          message: all available catalogsources are healthy
          reason: CatalogSourcesAdded
          status: "False"
          type: CatalogSourcesUnhealthy
        - message: 'constraints not satisfiable: subscription self-node-remediation requires
            at least one of redhat-operators/openshift-marketplace/stable/self-node-remediation.v0.10.2,
            redhat-operators/openshift-marketplace/stable/self-node-remediation.v0.10.1,
            redhat-operators/openshift-marketplace/stable/self-node-remediation.v0.10.0,
            redhat-operators/openshift-marketplace/stable/self-node-remediation.v0.9.0,
            redhat-operators/openshift-marketplace/stable/self-node-remediation.v0.8.0 or
            redhat-operators/openshift-marketplace/stable/self-node-remediation.v0.7.1,
            subscription self-node-remediation exists, clusterserviceversion self-node-remediation.v0.10.2
            exists and is not referenced by a subscription, @existing/openshift-workload-availability//self-node-remediation.v0.10.2,
            redhat-operators/openshift-marketplace/stable/self-node-remediation.v0.10.2,
            redhat-operators/openshift-marketplace/stable/self-node-remediation.v0.10.1,
            redhat-operators/openshift-marketplace/stable/self-node-remediation.v0.10.0,
            redhat-operators/openshift-marketplace/stable/self-node-remediation.v0.9.0,
            redhat-operators/openshift-marketplace/stable/self-node-remediation.v0.8.0 and
            redhat-operators/openshift-marketplace/stable/self-node-remediation.v0.7.1 originate
            from package self-node-remediation'
          reason: ConstraintsNotSatisfiable
          status: "True"
          type: ResolutionFailed
        lastUpdated: "2025-10-29T14:42:09Z"

      [1] https://docs.redhat.com/en/documentation/workload_availability_for_red_hat_openshift/23.3/html/remediation_fencing_and_maintenance/self-node-remediation-operator-remediate-nodes#installing-self-node-remediation-operator-using-cli_self-node-remediation-operator-remediate-nodes

              vipikuma vipin kumar
              matthiasmuench Matthias Muench
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated: