quota enforcement can be bypassed by failed deployment

[tgross]

When allocations stop on the client, they update their status on the server and this credits the allocation's resources to any quota limits. If a job that goes over quota has an allocation that stops due to a placement failure (ex. wrong Docker image), submitting a new version of the job may cause the scheduler to issue an eviction for the stopped allocation. This double-credits the allocation's resources to the quota limit, and can result in a job bypassing quotas.

This issue has been fixed and will ship in Nomad Enterprise 1.1.1, and will be backported to Nomad 1.0.x.

[github-actions]

I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.