Bug 1874651

Summary:	creating pods is forbidden because the status is unknown for quota
Product:	OpenShift Container Platform	Reporter:	jooho lee <jlee>
Component:	openshift-apiserver	Assignee:	Lukasz Szaszkiewicz <lszaszki>
Status:	CLOSED WORKSFORME	QA Contact:	Xingxing Xia <xxia>
Severity:	high	Docs Contact:
Priority:	high
Version:	4.5	CC:	aos-bugs, cscribne, ggore, joedward, jokerman, lszaszki, maszulik, mfojtik, sttts
Target Milestone:	---	Keywords:	UpcomingSprint
Target Release:	4.8.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-02-05 12:49:02 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description jooho lee 2020-09-01 21:05:48 UTC

Description of problem:
clusterresourcequota was wokring properly before but at some point, it seems to be broken.

With this quota:
~~~
Name:		o-ade-dev-12
Created:	2 months ago
Labels:		template=ocp-cluster-quota
Annotations:	openshift.io/application-name=Tapestry
		openshift.io/poc=false
		openshift.io/project-admin-email=mribeiro.com
		openshift.io/project-admin-id=michael.ribeiro
		openshift.io/project-admin-name=Ribeiro, Michael
		openshift.io/quota-owner-email=al.bastien
		openshift.io/quota-owner-id=al.bastien
		openshift.io/quota-owner-name=Bastien, Al
Namespace Selector: ["tapestry-poc" "omf-poc-cgi"]
Label Selector:
AnnotationSelector: map[openshift.io/quota-id:o-ade-dev-12]
Scopes:									NotTerminating
Resource								Used	Hard
--------								----	----
limits.cpu								58	80
limits.memory								49Gi	60G
px-block-norep.storageclass.storage.k8s.io/requests.storage		0	0
px-block-replicated.storageclass.storage.k8s.io/requests.storage	0	0
px-file-norep.storageclass.storage.k8s.io/requests.storage		0	0
px-file-replicated.storageclass.storage.k8s.io/requests.storage		0	56G
requests.cpu								6500m	8
requests.memory								24832Mi	60G
stork-snapshot-sc.storageclass.storage.k8s.io/requests.storage		0	0

~~~

px-file-replicated can not claim more than 56G but there are 62G PVC created under the project. The weird thing is the used amount is 0.

It might not calculate created PVC's request amount.



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


How reproducible:

Not found reproduce way.

Steps to Reproduce:
1.
2.
3.

Actual results:
End user can create new PVCs.

Expected results:
A new pvc can not be created because it hits the quota

Additional info:

Comment 3 Maciej Szulik 2020-09-08 10:04:26 UTC

Sending this api&auth team.

Comment 4 Lukasz Szaszkiewicz 2020-09-11 09:07:01 UTC

moving to the next sprint.

Comment 28 Lukasz Szaszkiewicz 2021-02-05 12:49:02 UTC

This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason. As such, we're closing this bug.

If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.