getProjectListStorageStatisticsEE does not return any data
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Summary
Owners of a top level group cannot see any storage data.
Steps to reproduce
- Be an owner of a group
- Go to https://gitlab.com/groups/GROUP_HERE/-/usage_quotas#storage-quota-tab
- Observe the table being empty
Example Project
/
What is the current bug behavior?
No data is being returned by the graphQL API. The request is a 200 but the array is empty.
This is further confirmed by going to the https://gitlab.com/-/graphql-explorer page and searching with:
GraphQL request
query getProjectListStorageStatisticsEE($fullPath: ID!, $searchTerm: String = "", $first: Int, $last: Int, $after: String, $before: String, $sortKey: NamespaceProjectSort) {
namespace(fullPath: $fullPath) {
id
projects(
includeSubgroups: true
notAimedForDeletion: true
search: $searchTerm
first: $first
last: $last
after: $after
before: $before
sort: $sortKey
) {
nodes {
id
fullPath
nameWithNamespace
avatarUrl
webUrl
name
statistics {
storageSize
costFactoredStorageSize
repositorySize
lfsObjectsSize
containerRegistrySize
buildArtifactsSize
packagesSize
wikiSize
snippetsSize
__typename
}
__typename
}
pageInfo {
...PageInfo
__typename
}
__typename
}
__typename
}
}
fragment PageInfo on PageInfo {
hasNextPage
hasPreviousPage
startCursor
endCursor
__typename
}
GraphQL Variables
{
"searchTerm": "",
"fullPath": "TOP_LEVEL_GROUP_HERE",
"first": 20,
"sortKey": "EXCESS_REPO_STORAGE_SIZE_DESC"
}
What is the expected correct behavior?
The table has data.
Relevant logs and/or screenshots
Customer attached this screenshot showing the output:
Kibana shows this request being a 200 - https://log.gprd.gitlab.net/app/r/s/MbvdC so no errors are returned.
Output of checks
This bug happens on GitLab.com
GitLab Enterprise Edition 18.3.0-pre 6235e90b
Possible fixes
Patch release information for backports
If the bug fix needs to be backported in a patch release to a version under the maintenance policy, please follow the steps on the patch release runbook for GitLab engineers.
Refer to the internal "Release Information" dashboard for information about the next patch release, including the targeted versions, expected release date, and current status.
High-severity bug remediation
To remediate high-severity issues requiring an internal release for single-tenant SaaS instances, refer to the internal release process for engineers.
