Uploaded image for project: 'Distributed Tracing'
  1. Distributed Tracing
  2. TRACING-3756

detectAutoscalingVersion always picks autoscaling/v2beta2 instead of autoscaling/v2 if both APIs are available

    • Icon: Bug Bug
    • Resolution: Done-Errata
    • Icon: Undefined Undefined
    • rhosdt-3.1
    • None
    • None
    • None
    • 2
    • False
    • None
    • False
    • Tracing Sprint # 246

          [TRACING-3756] detectAutoscalingVersion always picks autoscaling/v2beta2 instead of autoscaling/v2 if both APIs are available

          Errata Tool added a comment -

          Since the problem described in this issue should be resolved in a recent advisory, it has been closed.

          For information on the advisory (Low: Red Hat OpenShift distributed tracing 3.1.0 operator/operand containers), and where to find the updated files, follow the link below.

          If the solution does not work for you, open a new bug report.
          https://access.redhat.com/errata/RHSA-2024:0998

          Errata Tool added a comment - Since the problem described in this issue should be resolved in a recent advisory, it has been closed. For information on the advisory (Low: Red Hat OpenShift distributed tracing 3.1.0 operator/operand containers), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2024:0998

          Israel Blancas Alvarez (Inactive) added a comment - https://github.com/jaegertracing/jaeger-operator/issues/2367

            rhn-support-iblancas Israel Blancas Alvarez (Inactive)
            ploffay@redhat.com Pavol Loffay
            Ishwar Kanse Ishwar Kanse
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: