You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 23, 2020. It is now read-only.
I've an openshift account that has already exhausted its quota and there are a few apps running in stage/prod envs. I can start a new build to deploy an app and Jenkins reports that the app deployment went fine while it failed with quota errors behind the scene. There are no errors in Jenkins logs. OSIO does not report any errors either. Openshift thankfully sheds light into the problem with the following error.
Error creating: pods "vertx1-5-" is forbidden: exceeded quota: compute-resources, requested:
limits.cpu=1,limits.memory=512Mi, used: limits.cpu=2,limits.memory=1Gi, limited:
limits.cpu=2,limits.memory=1Gi
27 times in the last 2 hours
We should either prevent the build from starting or report an error in the build that quota is exhausted. Also tell people what to do at that point.
This bug is related, but it talks more about the parallelism aspect rather than resource exhaustion. #2729
The text was updated successfully, but these errors were encountered:
jaseemabid
changed the title
Appl deployments fail silently after quota is exhaused.
App deployments fail silently after quota is exhaused.
Apr 5, 2018
I've an openshift account that has already exhausted its quota and there are a few apps running in stage/prod envs. I can start a new build to deploy an app and Jenkins reports that the app deployment went fine while it failed with quota errors behind the scene. There are no errors in Jenkins logs. OSIO does not report any errors either. Openshift thankfully sheds light into the problem with the following error.
We should either prevent the build from starting or report an error in the build that quota is exhausted. Also tell people what to do at that point.
This bug is related, but it talks more about the parallelism aspect rather than resource exhaustion. #2729
The text was updated successfully, but these errors were encountered: