Git push fails due to 10GB project size limit even additional storage is available
Bug
Summary
A customer pre-purchase Additional storage for their group namespace while none of the project under the namespace has reached the 10GB limit. When the customer try to do git Push which cause the project to go above the 10GB limit, the push is rejected.
Steps to reproduce
- Purchase Additional Storage for a namespace when none of the project has reach the limit yet
- Do a git push to the project that would cause the project to go above the 10GB limit
- Observe the push being rejected
What is the current bug behavior?
Git push is rejected even though there's additional storage available for the group that the project is under.
What is the expected correct behavior?
Git push command should come through when there's additional storage available.
Relevant logs and/or screenshots
(Paste any relevant logs - please use code blocks (```) to format console output, logs, and code as it's tough to read otherwise.)
batch response: Your push has been rejected, because this repository has exceeded its size limit of 10 GB by 660 MB. Please contact your GitLab administrator for more information.
Uploading LFS objects: 0% (0/30), 0 B | 0 B/s, done.
Workarounds
Reach out to support so we can manually change the limit as a workaround.
Reported examples
Edited by Firdaws Farukh