Uploaded image for project: 'Project Quay'
  1. Project Quay
  2. PROJQUAY-1788

Can't see quay in OCP monitoring dashboard when quay operator component Monitoring is true

XMLWordPrintable

      Description:

      This is an issue found when deploy quay with enabled monitoring component in QuayRegistry, after quay was deployed successfully, create some new users in Quay and create some organizations in quay, check OCP Monitoring panel, found can't see quay under dashboard, but can see and query quay metrics under OCP Metrics panel.

      Following guide: https://github.com/quay/quay-operator/pull/401 

      Quay Operator Version:

      oc get pod -n openshift-operators
      NAME                                    READY   STATUS    RESTARTS   AGE
      quay-operator.v3.5.0-5fcc69495c-nbl75   1/1     Running   0          28m
      
      oc get pod quay-operator.v3.5.0-5fcc69495c-nbl75  -n openshift-operators -o json | jq '.spec.containers[0].image'
      "registry.redhat.io/quay/quay-operator-rhel8@sha256:eecc51864da39abaa48ae8568592c2c6cf2fa5a8d908f9b2e13f58c238d9e19c"
      
      oc get quayregistry quayaws3 -o json | jq '.spec.components[6]' {   "kind": "monitoring",   "managed": true }
      Can't see Quay in OCP Monitoring Dashboard:

       

      Can see and query Quay metrics in OCP Monitoring Metrics:

      Steps:

      1. Deploy Quay 3.4.5 Operator to all OCP namespace
      2. Deploy quay with quay 3.5 Operator with set "monitoring as true"
      3. Create some new users in quay and some new orgs in quay
      4. Check OCP Monitoring dashboard

      Expected Results:

      Can see quay under OCP Monitoring dashboard

      Actual Results:

      Can't see quay under OCP Monitoring dashboard

              jonathankingfc Jonathan King
              lzha1981 luffy zhang
              Dongbo Yan Dongbo Yan
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: