Projects can not be sorted by consumed quota in "Project Quotas"

[fivezerosix]

Expected behavior and actual behavior:
The project quotas view uses the column names as a sorting mechanism. By clicking the name you would be able to sort the most consuming project or the least.

The column name not longer has that behavior, making it difficult to extract quick insights.

We even tried the old API call: api/v2.0/quotas?reference=project&page=1&page_size=15&sort=-used.storage
and the JSON returned objects unsorted.

Steps to reproduce the problem:
From the left hand side menu clic "Project Quotas" -> The storage column can no longer be sorted by clicking it:

Versions:
Please specify the versions of following systems.

• Harbor version: v2.3.5-239680cd
• Working Version: v2.2.4-1bc848b3

Please let me know if i can provide anything else useful.

[lindhe]

Sorry if I'm hijacking the discussion, but is the bytes used ever updated? I can only see "0Byte of ..." in my projects, regardless of what limit they have. And that's what I see in your screenshot too. I guess that needs to be fixed first before there's anything to sort by...

Or does that work for anyone else?

[AllForNothing]

@lindhe
Never seen the issue you mentioned.
Do you have any artifacts in each project? And What's the used storage returned from quota API?

[lindhe]

Yeah, we have ~1TiB on disk.

Thanks for the suggestion. I've checked the quotas request now, and they too say that it's 0.

{
  "8": {
    "creation_time": "2022-03-09T13:03:04.393Z",
    "hard": {
      "storage": 1099511627776
    },
    "id": 8,
    "ref": {
      "id": 7,
      "name": "project-1",
      "owner_name": ""
    },
    "update_time": "2022-03-09T13:03:04.393Z",
    "used": {
      "storage": 0
    }
  }
}

We use Azure Blob Storage as backend. Could that be why it's 0?

[AllForNothing]

@wy65701436 can you help to explain this?

[lindhe]

Should I open a new issue for this? I don't want to clutter this discussion if my issue is not really related to OP's request.

[github-actions]

This issue is being marked stale due to a period of inactivity. If this issue is still relevant, please comment or remove the stale label. Otherwise, this issue will close in 30 days.

[github-actions]

This issue is being marked stale due to a period of inactivity. If this issue is still relevant, please comment or remove the stale label. Otherwise, this issue will close in 30 days.

[github-actions]

This issue is being marked stale due to a period of inactivity. If this issue is still relevant, please comment or remove the stale label. Otherwise, this issue will close in 30 days.

[github-actions]

This issue is being marked stale due to a period of inactivity. If this issue is still relevant, please comment or remove the stale label. Otherwise, this issue will close in 30 days.

[github-actions]

This issue was closed because it has been stalled for 30 days with no activity. If this issue is still relevant, please re-open a new issue.

[github-actions]

This issue is being marked stale due to a period of inactivity. If this issue is still relevant, please comment or remove the stale label. Otherwise, this issue will close in 30 days.

[github-actions]

This issue was closed because it has been stalled for 30 days with no activity. If this issue is still relevant, please re-open a new issue.