Uploaded image for project: 'AMQ Broker'
  1. AMQ Broker
  2. ENTMQBR-8664

AMQ Broker operator pod not starting, with error "unable to retrieve the complete list of server APIs: external.metrics.k8s.io/v1beta1"

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done-Errata
    • Icon: Undefined Undefined
    • None
    • AMQ 7.11.5.OPR.1.GA
    • operator
    • False
    • None
    • False
    • User Experience
    • Workaround Exists
    • Hide

      Check all monitoring pods are up and running. Start or reboot the ones that are not running.

      There is some monitoring pod that is stopped (Dynatrace, on the ticket particular case), and it makes those metrics unavailable

      Diagnostic Steps

      1. You can check the monitoring API status with the command:

      $ oc api-resources
      You may see the same error described above, showing up in the command output results

      2. Then, you get additional details with

      $ oc get apiservices | grep metrics
      The command output showed that a dynatrace related service was down.

      3. We switched to the dynatrace namespace and found that the dynatrace API server pod deployment had been scaled to 0 replicas for some reason; after scaling this deployment up, the AMQ Broker Operator pod was eventually able to start and the application setup moved forward.

      Show
      Check all monitoring pods are up and running. Start or reboot the ones that are not running. There is some monitoring pod that is stopped (Dynatrace, on the ticket particular case), and it makes those metrics unavailable Diagnostic Steps 1. You can check the monitoring API status with the command: $ oc api-resources You may see the same error described above, showing up in the command output results 2. Then, you get additional details with $ oc get apiservices | grep metrics The command output showed that a dynatrace related service was down. 3. We switched to the dynatrace namespace and found that the dynatrace API server pod deployment had been scaled to 0 replicas for some reason; after scaling this deployment up, the AMQ Broker Operator pod was eventually able to start and the application setup moved forward.
    • Critical

      The AMQ broker operator pod does not start, after migrating the Openshift version. Because of this, AMQ Broker deployments cannot be added or updated

      The following message can be seen on the AMQ Operator pod's logs

      I1214 16:18:12.127091 1 request.go:665] Waited for 1.843370465s due to client-side throttling, not priority and fairness, request: GET:https://172.21.0.1:443/apis/packages.operators.coreos.com/v1?timeout=32s
      2023-12-14T16:18:19.478Z ERROR setup failed in detecting openshift {"error": "unable to retrieve the complete list of server APIs: external.metrics.k8s.io/v1beta1: the server is currently unable to handle the request"}
      main.main
      /workspace/app/main.go:187
      runtime.main
      /opt/rh/go-toolset-1.17/root/usr/lib/go-toolset-1.17-golang/src/runtime/proc.go:255
      {{}}

              gtully@redhat.com Gary Tully
              rhn-support-anarvaez Alfredo Narvaez
              Mikhail Krutov Mikhail Krutov
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: