STORAGE BUG: A storage purchase didn’t unlock a project for a customer
Summary
A storage purchase for the client didn't unblock the project. The purchase was successful and the Usage Quotas
page was showing Purchased storage available as 28.3 out of 30 Gib. Despite that, the customer's project was blocked in read-only mode.
The project in question is nested under another namespace. Not sure if that is related though.
Steps to reproduce
Issue is reproducible for locked projects in a sub-group:
- Create sub-group
- Create a project in the sub group with at least one file (e.g. 2mb file)
- Set a low repo size limit (e.g. 1mb) so that the storage limit is reached by that repo (via Admin > Settings > General > Account and limit > Size limit per repository)
- Purchase a storage pack to unlock the namespace
- Attempt to create a new branch in the project - error shown as below
What is the current bug behavior?
The project wasn't unblocked.
What is the expected correct behavior?
Once the storage purchase is completed all the project over 10Gb should be unlocked if there is anough additional storage.
Relevant logs and/or screenshots
Kibana logs about rejecting push: https://log.gprd.gitlab.net/goto/f086203335b19efeed4424ea34a39682. There you can see the POST attempting to create the branch test_test
and then a reply back when querying /api/:version/internal/allowed
with a status code of 401
Workarounds
An admin user can manually adjust storage limit for the specific project.
Reported examples
- https://gitlab.zendesk.com/agent/tickets/182522
- https://gitlab.zendesk.com/agent/tickets/185258
- https://gitlab.zendesk.com/agent/tickets/184715
- https://gitlab.zendesk.com/agent/tickets/186346
- https://gitlab.zendesk.com/agent/tickets/185306
- https://gitlab.zendesk.com/agent/tickets/186907
- https://gitlab.zendesk.com/agent/tickets/190409