+++ This bug was initially created as a clone of Bug #1904026 +++ The quota controllers act on resources retrieved from the discovery endpoint which might contain only a fraction of all resources due to a network error. Both controllers should periodically resync when new resources are observed from the discovery. Additionally, the CRQ should always ensure the current set of monitors are running. The CRQ should not block when new resources are observed (deadlock).
*** Bug 1906649 has been marked as a duplicate of this bug. ***
Confirmed with latest payload: 4.6.0-0.nightly-2020-12-13-230909, the issue has fixed: [root@dhcp-140-138 ~]# oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.6.0-0.nightly-2020-12-13-230909 True False 17m Cluster version is 4.6.0-0.nightly-2020-12-13-230909 Follow steps: 1) Scale down the CVO to replicas==0; 2) Chang the openshiftapiservers to Unmanaged status; 3) Scale down the openshift apiserver to 0, to turn off the openshift-apiserver; 4) restart all KCMs; 5) Turn on the openshift-apiserver; 6)Create test project and imagestream resource and quota about imagestream: 7) Delete all the imagestream, check the quota : [root@dhcp-140-138 ~]# oc get quota test1 NAME AGE REQUEST LIMIT test1 15s openshift.io/imagestreams: 1/10 [root@dhcp-140-138 ~]# oc get is NAME IMAGE REPOSITORY TAGS UPDATED rails-postgresql-example image-registry.openshift-image-registry.svc:5000/zhouyt/rails-postgresql-example [root@dhcp-140-138 ~]# oc delete all --all ...... [root@dhcp-140-138 ~]# oc get is No resources found in zhouyt namespace. [root@dhcp-140-138 ~]# oc get quota test1 NAME AGE REQUEST LIMIT test1 90s openshift.io/imagestreams: 0/10
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Important: OpenShift Container Platform 4.6.9 security and bug fix update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2020:5614