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

Cannot start new Pod if Completed/Error count reached quota max already

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Minor Minor
    • None
    • 4.12
    • Dev Console
    • No
    • ODC Sprint 3248
    • 1
    • Rejected
    • False
    • Hide

      None

      Show
      None

      Description of problem:

      Cannot start new pod if Completed/Error count is over quota max already

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

      4.12

      How reproducible:

      Alway

      Steps to Reproduce:

      1. Within Dev sandbox and Administration/Resource Quotas area could see that quotas for Pods max is 50
      2. At the moment have such situation (here via remote oc login from my Linux box):
      
      For Completed pods:
      $ oc get pod | grep 'Completed' | wc -l
      49
      
      For Error pods:
      $ oc get pod | grep 'Error' | wc -l
      1
      
      So total is 50, but no running Pods.
        
      3. I cannot even start then Web console in such case, cause that is under same quota and cannot spin Tools pod with oc CLI :(
      

      Actual results:

      Cannot start any more pods

      Expected results:

      Should be able to start new pods if others are already in Completed or Error state

      Additional info:

       

            avik6028 Avik Kundu
            andrejusc@yahoo.com Andrejus Chaliapinas (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: