OpenShift GitOps Operator v1.2.0 sync failed with grpc errors in RHOCP 4

Solution Verified - Updated -

Issue

  • OpenShift GitOps Operator v1.2.0 sync failed with the below error.
rpc error: code = Unavailable desc = all SubConns are in TransientFailure, latest connection error: connection error: desc = "transport: Error while dialing dial tcp <Internal k8s IP>:8081: connect: connection refused"
  • The repo pods and app-controller pods enter a crashloopbackoff state eventually with the below errors.
$ oc logs pod/openshift-gitops-application-controller-0
"<time>" level=info msg="Normalized app spec: {\"status\":{\"conditions\":[{\"lastTransitionTime\":\"time\",\"message\":\"rpc error: code = Unknown desc = unexpected client error: unexpected requesting \\\"https://bitbucket.<url>refs?service=git-upload-pack\\\" status code: 502\",\"type\":\"ComparisonError\"}]}}" application=openshift-etcd-backup

Environment

  • Red Hat OpenShift Container Platform.
    • 4.x
  • Red Hat OpenShift GitOps Operator
    • 1.2.0

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