Red Hat OpenShift Pipelines Operator Custom Resource Definitions are stuck in the resource being deleted state.

Solution Verified - Updated -

Environment

  • Azure Red Hat OpenShift (ARO 4)
  • Red Hat OpenShift Container Platform (RHOCP)

Issue

  • Failed to install Red Hat OpenShift Pipelines Operator.
  • The Red Hat OpenShift Pipelines Operator Custom resource definitions are stuck in the resource being deleted state.
  • Red Hat OpenShift Pipelines Operator operator is deleted first before deleting Red Hat OpenShift Pipelines Operator custom resource definitions.

Resolution

  • Install the Red Hat OpenShift Pipelines Operator per the document.

  • Delete Custom Resource Definitions stuck in the Resource being deleted state per Deleting the custom resources.

  • Check and delete all pipeline resources.

$ oc get all -A | grep -i pipelines

  • Uninstall the Red Hat OpenShift Pipelines Operator per the document.

  • Check if the Red Hat OpenShift Pipelines Operator is existing or not. If it is still existing then delete it.

$ oc get operators | grep -i pipelines

$ oc delete operators openshift-pipelines-operator-rh.openshift-operators
  • Reinstall the Red Hat OpenShift Pipelines Operator per the document.

Root Cause

  • Per the document, it is necessary to delete the Red Hat OpenShift Pipelines Operator Custom Resource Definition first before deleting the Red Hat OpenShift Pipelines Operator operator.

  • If the Red Hat OpenShift Pipelines Operator operator is removed first before deleting Red Hat OpenShift Pipelines Operator Custom Resource Definitions then the custom resource definitions may get stuck in the resource being deleted state.

Diagnostic Steps

  • Check the Red Hat OpenShift Pipelines Operator is deleted per the document.

  • Check the Red Hat OpenShift Pipelines Operator is deleted first before deleting the Custom Resource Definitions.

  • Check the Custom Resource Definitions for the Red Hat OpenShift Pipelines operator are stuck in the Resource being deleted state.

  • Check the Tekton installer sets are in an error state.

$ oc get tektoninstallerset
  • Check the components are in a not-ready state.
$ oc get tektonconfig config -o yaml

message: 'Components not in ready state: TektonPipeline: reconcile again and proceed'

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