The `openshift-gitops-controller-manager` pod is in CrashLoopBackOff state after the GitOps operator upgrade

Solution Verified - Updated -

Issue

  • The openshift-gitops-controller-manager pod is in CrashLoopBackOff and getting restarted continuously with the below mentioned errors in the pod logs:
Error from server: conversion webhook for argoproj.io/v1alpha1, Kind=ArgoCD failed: Post "https://openshift-gitops-operator-controller-manager-service.<namespace_name>.svc:443/convert?timeout=30s": no endpoints available for service "openshift-gitops-operator-controller-manager-service"
  • The GitOps operator is not able to upgrade as openshift-gitops-controller-manager pod is stuck in CrashLoopBackOff state.

Environment

  • Red Hat OpenShift Container Platform (RHOCP)
    • 4
  • Red Hat OpenShift GitOps
    • 1.10.z+

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