Resolved and Known Issues
Resolved Issues
#250040
The following tables provide a list of known issues as well as customer-reported issues, listed by release. All tables are sorted by Densify's Internal Reference number.

Issues resolved in each release are listed below:

No customer-reported issues were resolved in this release.

Internal |
Team Support Reference |
Description |
CRB-52705 |
69868 |
Resolved an issue related to performing T2C analyses. |
CRB-52710 |
71344 |
Resolved an issue related to deletion of control environments with no clusters. |
CRB-52734 |
73084 |
Resolved an issue related to performance of loading and working with the Analysis Rulesets page. |

Internal |
Team Support Reference |
Description |
CRB-51904 |
|
Resolved an issue related to inconsistencies in access to a locked user account. |
CRB-52603 |
71996 |
Resolved an issue related to user verification via reCAPTCHA. |
CRB-52611 |
72183 |
Resolved an issue that prevented users from logging in via Open ID. |
CRB-52612 |
71995 |
Resolved an issue that caused RDB loading to fail when an attribute value is an empty string. |
CRB-52629 |
72561 |
Resolved an issue related to the report, "History of Cluster Capacity in VM Units" failing to load. |

Internal |
Team Support Reference |
Description |
CRB-51165 |
64765 |
Completed the updates required to resolve the issue related to performance of the Optimization Overview dashboard and the EC2 tab in the Densify UI. The required updates were started in the previous release. |
CRB-52301 |
70069 |
Resolved an issue related to excluding hours from the Densify analysis. |

Internal |
Team Support Reference |
Description |
CRB-51165 |
64765 |
Resolved an issue related to performance of the Optimization Overview dashboard and the EC2 tab in the Densify UI. Additional performance updates will be delivered in the next release. |
CRB-52166 |
69439 |
Resolved an issue related to data collection in very large environments when using the Java-based audit. Security tokens in the AWS client instance are now refreshed before they expire. |

Internal |
Team Support Reference |
Description |
CRB-50479 |
53628 |
Resolved an issue related to loading of a specific set of Azure audit data. |
CRB-51641 |
51195 |
Resolved an issue related to a query running too long and blocking other jobs. |
CRB-51914 |
67424 |
Resolved an issue related to the footnote not being visible after clicking on a savings opportunity value in the Public Cloud Optimization for AWS dashboard. |
CRB-51974 |
67782 |
Resolved an issue related to VMs showing incorrect 'VM Memory HotAdd' status. The Densify Connector has also been updated to v2.2.4.6 to resolve this issue. |
CRB-51983 |
67601 |
Resolved an issue with some GCP systems missing from the Densify reports. |
CRB-52026 |
68013 |
Resolved an issue related to sizing recommendations in the Control Console that are not aligned with CPU utilization and cloud catalog options specified in the policy. |

Internal |
Team Support Reference |
Description |
CRB-51435 |
62498 |
Resolved an inconsistency in reporting of predictedUptime and totalHoursRunning. |
CRB-51564 |
63508 |
Resolved an issue related to the collection of Azure subscriptions being capped at 1000. |
CRB-51579 |
62740 |
Resolved an issue related to SLCO target host recommendations. |

Internal |
Team Support Reference |
Description |
CRB-50348 |
53956 |
Resolved an issue related to the Cloud System Sizing extension logic. |
CRB-51076 |
59008 |
Resolved an issue related to using the Group By feature on the Containers > Data tab. |
CRB-51136 |
59996 |
Resolved an issue related to how estimated effort is reported in the Densify UI and the API. |
CRB-51139 |
58687 |
Resolved an issue related to an upsizing container request and limit values. |
CRB-51208 |
60647 |
Resolved an issue related to using the drill down to the Instance Details, when working with customized groupings to filter data on the Public Cloud Optimization Overview page. |
CRB-51290 |
|
Resolved an issue related to excluding the AWS Government platforms from the savings plan analysis. |
CRB-51360 |
61183 |
Resolved an issue related to the following error message: Error updating database. Cause: java.sql.SQLException: Violation of PRIMARY KEY constraint. |

Internal |
Team Support Reference |
Description |
CRB-50085 |
50933 |
Resolved an issue related to Azure data collection failing due to ambiguous system matches. Storage accounts details are not used in any Densify analysis and have been removed from both the discovery and details data collection modules. |
CRB-51076 |
59008 |
Resolved an issue related to using the Group By feature on the Containers > Data tab. |
Resolved Issues - Densify Connector
Issues resolved in each release are listed below:

Internal |
Team Support Reference |
Description |
CRB-52760 |
72867 |
Resolved an issue related to the set of cipher suites that are included in the JRE version. The installed JRE version has been updated to AdoptOpenJDK 11.0.10_9. |
CRB-53839 |
|
Hotfix #1—Support shortname matching in VMware action automation. |
CRB-54616 |
90296 |
Hotfix #2—Resolved a vROps connection issue. |
Internal |
Team Support Reference |
Description |
CRB-52683 |
|
Resolved an issue related to incomplete execution of Action Automation. |
Internal |
Team Support Reference |
Description |
DC-292 |
71376 |
Updated to include the Spring 5.3.19 jar files, as per CVE-2022-22950. |
Internal |
Team Support Reference |
Description |
CRB-51974 |
67782 |
Updated to address an issue related to VMs showing incorrect 'VM Memory HotAdd' status. Densify has also been updated to resolve this issue. |
Internal |
Team Support Reference |
Description |
CRB-51669 |
|
Updated to address an issue related to vROps data collection performance issues related to token-based authentication. |
Internal |
Team Support Reference |
Description |
CRB-51237 |
|
Updated to return a VMware data collection module used for custom integrations. You must re-install this version of the connector to get this update. |
Internal |
Team Support Reference |
Description |
CRB-51544 |
|
Updated to include the Apache 2.17.1 jar files, as per CVE-2021-45046 and CVE-2021-45105, after the issue was initially reported in CVE-2021-44228. You must re-install this version of the connector to get this update. |
2.2.4.1 and 2.2.4.2 - January 4, 2022
Internal |
Team Support Reference |
Description |
CRB-51544 |
|
Updated to include the Apache 2.17.1 jar files, as per CVE-2021-45046 and CVE-2021-45105, after the issue was initially reported in CVE-2021-44228. To fix this security vulnerability, you must add the 4 files from the v2.17.1 jar to your connector installation. See |
Internal |
Team Support Reference |
Description |
CRB-51544 |
|
Updated to include the Apache 2.15 jar files, as per CVE-2021-44228. You must re-install this version of the connector to get this update. |