Release notes
Fixed issues
Suggest changes
PDFs
Issues that were found in previous releases of NetApp Keystone STaaS services have been fixed in later releases. These are the fixes.
| Issue Description | After the fix | Fixed in release |
|---|---|---|
Incorrect tooltip text for the Current Burst index icon in the Capacity Trend tab. |
Displays the correct tooltip text "The amount of burst capacity currently being consumed. Note this is for current billing period, not the selected date range." |
March 28, 2024 |
Information on AQoS non-compliant volumes and MetroCluster partners is unavailable for AutoSupport subscriptions if Keystone data is not present for 24 hours. |
Fixed |
March 28, 2024 |
Occasional mismatch in the number of AQoS non-compliant volumes listed on the Volume Summary and Volume Details tabs if there are two service levels assigned to a volume that fulfils AQoS compliance for only one service level. |
Fixed |
March 28, 2024 |
No information is available on the Assets tab for AutoSupport subscriptions. |
Fixed |
March 14, 2024 |
If both MetroCluster and FabricPool were enabled in an environment where rate plans for both tiering and object storage were applicable, the service levels could be incorrectly derived for the mirror volumes (both constituent and FabricPool volumes). |
Correct service levels are applied to mirror volumes. |
February 29, 2024 |
For some subscriptions having a single service level or rate plan, the AQoS compliance column was missing in the CSV output of the Volumes tab reports. |
The compliance column is visible in the reports. |
February 29, 2024 |
In some MetroCluster environments, occasional anomaly was detected in the IOPS density charts in the Performance tab. This happened due to inaccurate mapping of volumes to service levels. |
The charts are correctly displayed. |
February 29, 2024 |
The usage indicator for a burst consumption record was being displayed in amber. |
The indicator appears in red. |
December 13, 2023 |
The date range and data in the Capacity Trend, Current Usage, and Performance tabs were not converted to UTC timezone. |
The date range for query and data in all the tabs are displayed in UTC time (server timezone). The UTC timezone is also displayed against each date field on the tabs. |
December 13, 2023 |
There was a mismatch in the start date and end date between the tabs and the downloaded CSV reports. |
Fixed. |
December 13, 2023 |