You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Sravani Revuri (Jira)" <ji...@apache.org> on 2026/10/16 13:09:00 UTC

[jira] [Updated] (HDDS-17074) [UI] Quota initializing state is not detected in Namespace Usage metadata

     [ https://issues.apache.org/jira/browse/HDDS-17074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sravani Revuri updated HDDS-17074:
----------------------------------
    Description: 
In nuMetadata.tsx, the quota response is checked with quotaResponse.state === 'INITIALIZING'. The /api/v1/namespace/quota endpoint returns status, not state, so the check never matches. As a result, the "quota is currently initializing" error is never shown, and the component treats the response as valid quota data.

Fix: Change quotaResponse.state to quotaResponse.status, matching the summary check above it. Add a test assertion that showDataFetchError is called with the quota-initializing message when /namespace/quota returns INITIALIZING.

found here: https://github.com/apache/ozone/pull/11513#discussion_r4269228317

  was:
In nuMetadata.tsx, the quota response is checked with quotaResponse.state === 'INITIALIZING'. The /api/v1/namespace/quota endpoint returns status, not state, so the check never matches. As a result, the "quota is currently initializing" error is never shown, and the component treats the response as valid quota data.

Fix: Change quotaResponse.state to quotaResponse.status, matching the summary check above it. Add a test assertion that showDataFetchError is called with the quota-initializing message when /namespace/quota returns INITIALIZING.


> [UI] Quota initializing state is not detected in Namespace Usage metadata
> -------------------------------------------------------------------------
>
>                 Key: HDDS-17074
>                 URL: https://issues.apache.org/jira/browse/HDDS-17074
>             Project: Apache Ozone
>          Issue Type: Bug
>            Reporter: Sravani Revuri
>            Assignee: Sravani Revuri
>            Priority: Major
>
> In nuMetadata.tsx, the quota response is checked with quotaResponse.state === 'INITIALIZING'. The /api/v1/namespace/quota endpoint returns status, not state, so the check never matches. As a result, the "quota is currently initializing" error is never shown, and the component treats the response as valid quota data.
> Fix: Change quotaResponse.state to quotaResponse.status, matching the summary check above it. Add a test assertion that showDataFetchError is called with the quota-initializing message when /namespace/quota returns INITIALIZING.
> found here: https://github.com/apache/ozone/pull/11513#discussion_r4269228317



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org