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

status update in CLusterResourceQuota is not expected

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Won't Do
    • Icon: Normal Normal
    • None
    • 4.16
    • openshift-apiserver
    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • None
    • Moderate
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Description of problem:

          i am using multi-project quota(ClusterResourceQuota) i see one of the small issue in it,
      for ex: # Created quota with 100G
      
      now created one pvc with size 50G and name as test
      again if i try to create the pvc again with the same name test and size as 50G, it will throw an error as pvc with a name already exists. after this, the quota is updated the status with 100G usage
      and it takes some time to refresh it.
      
      I also would like to know.  at what interval does the default reconciliation is happen is there any way to force quota to consider only successfully created pvs
       

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

          4.16

      How reproducible:

          always

      Steps to Reproduce:

      1. create pvc with size 50G and name as test
      2. try to create the pvc again with the same name test and size as 50G, it will throw an error as pvc with a name already exists. after this, the quota is updated with extra 50G in status section
      
      and it takes some time to refresh it.      

      Actual results:

          Quota should not consider pvc size if it fails

      Expected results:

          

      Additional info:

          

              Unassigned Unassigned
              rchikatw@redhat.com Ritesh Chikatwar (Inactive)
              None
              None
              Rahul Gangwar Rahul Gangwar
              None
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: