After upgrading Red Hat OpenShift Service Mesh the pod of jaeger keeps on crashing

Solution Verified - Updated -

Issue

  • After upgrading Red Hat OpenShift Service Mesh's jaeger-operator from 1.13.1 to 1.17.4 the jaeger pod keeps crashing with CrashLoopBackoff status.

  • The following logs are observed in the jaeger container:

    2020/07/17 02:23:14 maxprocs: Leaving GOMAXPROCS=4: CPU quota undefined
unknown flag: --collector.grpc.tls.enabled
Error: unknown flag: --collector.grpc.tls.enabled
Usage:
jaeger-all-in-one [flags]
jaeger-all-in-one [command]

Environment

  • Red Hat OpenShift Container Platform
    • 4.4.9
  • Red Hat OpenShift Service Mesh
    • 1.1.4
  • Red Hat Jaeger Operator
    • 1.13.1
    • 1.17.4

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