PSI Cluster Quota resported as full without any resource consuming it. #2493
Labels
kind/bug
Categorizes issue or PR as related to a bug.
priority/important-soon
Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
Describe the bug
Noticing that pods are not getting terminated after their action has been completed.
https://console-openshift-console.apps.ocp4.prod.psi.redhat.com/k8s/ns/thoth-frontend-stage/pods
https://console-openshift-console.apps.ocp4.prod.psi.redhat.com/k8s/ns/thoth-frontend-stage/cronjobs/graph-refresh/jobs
thoth-application/graph-refresh/base/cronjob.yaml
Line 13 in 251d057
Another set of examples:
The job was terminated due to successful execution, however, the pods are still present
https://console-openshift-console.apps.ocp4.prod.psi.redhat.com/k8s/ns/thoth-frontend-stage/pods/graph-refresh-27483880-7c6fb
https://console-openshift-console.apps.ocp4.prod.psi.redhat.com/k8s/ns/thoth-frontend-stage/jobs/graph-refresh-27483880
The various namespaces are reporting resource quota full. ex:
![frontend](https://user-images.githubusercontent.com/14028058/161521041-08c9b59e-62ed-4060-8e0a-63b8568f3b74.png)
Seems like once the quota is set and used by pods it is not getting reset.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Quota is freed up for other resources to run in a timing fashion
Additional context
This affects all the stage deployments.
cluster: ocp4-stage and ocp4-test
Thread link: https://chat.google.com/room/AAAAVjnVXFk/NAw7nZ1IKdw
The text was updated successfully, but these errors were encountered: