Known Issues
Known Issues in the Current Release
Known Issues in the Current Release
Internal Reference | Team Support Reference | Densify Version | Description |
---|---|---|---|
CRB-53733 | v1.1.0 | The drill down instance count is not correct for GCP accounts, when using the Group By > “Account”, option Navigate to Optimization Overview > Data tab and then set Group By to “Account” and then click the hyperlink from the GCP counts and when you drill down to the Details page, you will observe that the count at the top of the report does not match the count shown on the main page. This only occurs for GCP when you set Group By to “Account”. As a workaround, navigate to the Public Cloud > Google Cloud summary page where the drill down counts are correct. | |
PD-54190, PD-54829 | v2.4 | In the Optimization Overview > Data tab > Allocations and Utilization tab, some values may not match the aggregated totals shown in the tabular report at the top of the page. This is due to how ASG and VM scale set utilization is calculated for this dashboard. | |
PD-54831 | v2.4 | The exception, “Error: PKIX path building failed, JDBCConnect:FAILED for mssqlserverbcp”, can be ignored. This error is benign no any consequential errors were discovered due to mssqlserverbcp connection failure, during testing. | |
PD-55135 | v2.4 | The following API calls are not currently supported for VM Scale Set.
| |
PD-55188 | v2.4 | The Impact Analysis and Recommendation Report report is not currently available for VM Scale Sets with maximum size >1. The API call has not been disabled and a report is generated which has incorrect data. | |
PD-56033 | v2.6 | On the Node Group Health page when using the table filter, and then clicking the “Unique Nodes” hyperlink to drill down to the Nodes page, the Node page displays all of the nodes and not the filtered list, as expected. | |
PD-57737 | v2.6 | When you export the AI Analysis Details page some formatting, like color coding has been lost. The formatting, that makes the spreadsheet easier to read, will be returned in a future release. | |
PD-56688 | v2.10 | When modifying user accounts users must log out and clear their browser before logging in again. This is required regardless of the type or version of browser you are using. | |
v3.0 | When the new nav bar configuration setting is set tot true, it enables both container and cloud nvigation bars. So users see both the Container and Cloud UI. This is an issue for cloud-only users. |
Densify Resolved Issues
Issues resolved in each release are listed below:3.4.0 July 9, 2025
3.4.0 July 9, 2025
Internal Reference | Team Support Reference | Description |
---|---|---|
PD-57783 | Resolved an issue related to how data is aggregated and saving new views with customized data aggegation. | |
PD-58076 | Resolved the discrepancy between recommended ASG/VMSS values in the UI and through the API. |
3.2.0 June 11, 2025
3.2.0 June 11, 2025
Internal Reference | Team Support Reference | Description |
---|---|---|
PD-56983 | Resolved an issue where the link between the node group and its containers was missing. |
3.0 April 23, 2025
3.0 April 23, 2025
Internal Reference | Team Support Reference | Description |
---|---|---|
PD-56932 | Resolved an issue related to viewing Kubex on various screen sizes. | |
PD-57398 | Resolved an issue related inconsistencies in Kubex view/filter tree viewer counts. | |
PD-57507 | Resolved an issue related to the values in the license_weight_factor table. | |
PD-57546 | Resolved an issue related to incorrect memory conversion when using the API. |
Data Forwarder Resolved Issues
4.2.0 - May 15, 2024
4.2.0 - May 15, 2024
Internal Reference | Team Support Reference | Description |
---|---|---|
PD-57371 | The data forwarder fails on HPA configured to scale on more than one metric. |
4.1.3 - April 1, 2024
4.1.3 - April 1, 2024
Internal Reference | Team Support Reference | Description |
---|---|---|
PD-56983 | Resolved an issue related to nodes not being identified correctly and not being linked to their containers. |
4.1.2 - March 17, 2024
4.1.2 - March 17, 2024
Internal Reference | Team Support Reference | Description |
---|---|---|
PD-56238 | Resolved an issue related to node utilization exceeding 100%. |
4.1.1 - November 27, 2024
4.1.1 - November 27, 2024
Internal Reference | Team Support Reference | Description |
---|---|---|
PD-55817 | Resolved an issue related to CPU/Memory reservation percent value exceeding 100%. This value is calculated for nodes, node groups and clusters. |
4.1.0 - September 19, 2024
4.1.0 - September 19, 2024
Internal Reference | Team Support Reference | Description |
---|---|---|
PD-55482 | 94875 | Resolved an issue related to namespaces missing containers. |
4.0.0 - May 28, 2024
4.0.0 - May 28, 2024
Internal Reference | Team Support Reference | Description |
---|---|---|
CRB-54280 | Resolved an issue related to handling version changes and additions to kube-state-metrics. | |
CRB-54188 | Resolved an issue with Kubernetes Resource Quota metrics collection. | |
PD-52756 | Resolved an issue in which a panic condition was encountered during collection of NodeGroups data. | |
PD-54038 | Resolved an issue related to linking of readme.md files on Docker hub. |