Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-5787

ClusterResourceQuota values are not reflecting.


    • Important
    • Rejected
    • False
    • Hide



      This is a clone of issue OCPBUGS-723. The following is the description of the original issue:

      Description of problem:
      I have a customer who created clusterquota for one of the namespace, it got created but the values were not reflecting under limits or not displaying namespace details.
      $ oc describe AppliedClusterResourceQuota
      Name: test-clusterquota
      Created: 19 minutes ago
      Labels: size=custom
      Annotations: <none>
      Namespace Selector: []
      Label Selector:
      AnnotationSelector: map[openshift.io/requester:system:serviceaccount:application-service-accounts:test-sa]
      Scopes: NotTerminating
      Resource Used Hard
      -------- ---- ----

      WORKAROUND: They recreated the clusterquota object (cache it off, delete it, create new) after which it displayed values as expected.

      In the past, they saw similar behavior on their test cluster, there it was heavily utilized the etcd DB was much larger in size (>2.5Gi), and had many more objects (at that time, helm secrets were being cached for all deployments, and keeping a history of 10, so etcd was being bombarded).

      This cluster the same "symptom" was noticed however etcd was nowhere near that in size nor the amount of etcd objects and/or helm cached secrets.

      Version-Release number of selected component (if applicable): OCP 4.9

      How reproducible: Occurred only twice(once in test and in current cluster)

      Steps to Reproduce:
      1. Create ClusterQuota
      2. Check AppliedClusterResourceQuota
      3. The values and namespace is empty

      Actual results: ClusterQuota should display the values

      Expected results: ClusterQuota not displaying values

            jchaloup@redhat.com Jan Chaloupka
            openshift-crt-jira-prow OpenShift Prow Bot
            ying zhou ying zhou
            0 Vote for this issue
            5 Start watching this issue