Source and classification
- Source: ZNS Network Service 1.2.0 known issue record.
- Classification: Product issue.
- Confirmation basis: This behavior has been confirmed as a known issue in ZNS Network Service 1.2.0.
Issue metadata
- Issue ID: ZCF-5423.
- Component/product: Observability analysis and the ZNS collection pipeline.
- Status: Open.
- Priority/severity: P1.
- Affected version: 1.2.0.
Problem description
When an HTTP 401 authentication failure has actually occurred in the collection component, the page may still show ZNS Network Service as healthy, online, or collecting. The page status is inconsistent with the latest data timestamp.
Symptoms
- The page shows ZNS Network Service as healthy, online, or collecting.
- The latest timestamp of ZNS logs or metrics has stopped advancing.
- Relying only on the page status to determine whether collection is normal may cause a data interruption to be missed.
Impact
Logs or metrics may have stopped updating, and the data interruption cannot be identified promptly from the page status alone.
Workaround
- Use the page status only as a reference. To determine whether collection is normal, also check the timestamp of the latest log or metric.
- Have operations personnel check whether HTTP 401 errors continue to occur in the collection component and verify the platform credentials.
- After recording the environment information, an administrator can redistribute the log or monitoring collection configuration and wait for a collection cycle to verify new data.
Affected products
- Product: ZCF.
- Component: Network Service.
- Version: 1.2.0.
Fix status
- Current status: Pending fix.
- Related patch/fix package: No separate patch information is available.