OpenShift Upgrade is Stuck on 'Could not update namespace XYZ: the object is invalid, possibly due to local cluster configuration'

Solution Verified - Updated -

Issue

  • Upgrade to 4.13 is stuck showing:
Could not update namespace "openshift-operators" (619 of 842): the object is invalid, possibly due to local cluster configuration
  • The ClusterVersionOperator is show the following issue:
I0818 20:20:50.282233       1 sync_worker.go:1149] Update error 619 of 842: UpdatePayloadResourceInvalid Could not update namespace "openshift-operators" (619 of 842): the object is invalid, possibly due to local cluster configuration (*errors.StatusError: Namespace "openshift-operators" is invalid: metadata.ownerReferences: Invalid value: []v1.OwnerReference{v1.OwnerReference{APIVersion:"operator.tekton.dev/v1alpha1", Kind:"TektonPipeline", Name:"pipeline", UID:"5797eb97-d328-4290-ade3-68970b2ae01b", Controller:(*bool)(0xc08ac5a46a), BlockOwnerDeletion:(*bool)(0xc08ac5a46b)}, v1.OwnerReference{APIVersion:"config.openshift.io/v1", Kind:"ClusterVersion", Name:"version", UID:"0159559d-2b98-4581-b775-eff90fe844c9", Controller:(*bool)(0xc08ac5a46c), BlockOwnerDeletion:(*bool)(nil)}}: Only one reference can have Controller set to true. Found "true" in references for TektonPipeline/pipeline and ClusterVersion/version)

Environment

  • Red Hat OpenShift Container Platform 4.13

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content