Liquidware posts hotfixes for console components in the Liquidware Help Center HotFix KB
These include components like:
Mongo Version Updates
.Net Core updates
ProfileUnity Core Console side updates
Issue:
- Attempting to run the Mongo upgrade tool in a clustered environment results in the following prompt.
- Attempting to run the Mongo upgrade tool on a standalone/previously-clustered node results in the following prompt.
As of 7.0.26, Mongo has enforced mutual TLS communication and, as a result, now requires using certificates that contain both Server Authentication and Client Authentication enhanced key usage (EKU). Most certificates are generated only including Server Authentication, including the self-signed Mongo certificates created during the initial installation of ProfileUnity.
Limitations
-
In-place cluster upgrades are only possible for environments already using a certificate(s) that has both Server Authentication and Client Authentication (EKU) and are on the same major version of MongoDB.
Resolution
If an in-place upgrade is not possible due to the limitations mentioned above, we will need to tear-down the current cluster, return all nodes to standalone, upgrade them individually and then rebuild the cluster. This will necessarily cause interruption to user license validation and result in a notification box annoyance on any end-user's machine that happens to login during this change operation.
**NOTE** - If using a custom certificate, ensure a new certificate with both required EKU has already been created BEFORE tearing down the cluster as it will be required to replace the existing certificate at a later point when rebuilding the cluster.
On each node, one at a time:
- Backup the existing database by clicking Backup Databases under the Database section of the Administration page.
- Shutdown each ProfileUnity cluster node and take a snapshot prior to continuing. Once snapshots are completed, power back on all nodes and proceed below.
- Login to a node and navigate to the Clustering section of the Administration page and click Go to Standalone.
- Wait for the node to complete the operation. Log back into the node and confirm that it has successfully reverted to standalone mode.
- Repeat steps 3 and 4 for each node in the cluster before proceeding below.
- NOTE: If using a custom certificate, import the new certificate possessing both Client Authentication and Server Authentication into each node under the Web Services section of the Administration page.
- Run the Mongo upgrade utility on each node.
- NOTE: The default Mongo certificates are automatically recreated and the thumbprints within mongod.cfg and ProfileUnity.LicenseServer.exe.xml are updated with the new values.
- Once all nodes have been upgraded, proceed with re-enabling HA mode and adding back in the remaining nodes to the cluster. You can use this KB as a reference regarding that process: https://www.liquidware.com/support/articles/360019902611-Enabling-High-Availability-mode-in-6-8-x-for-redundant-processing-of-license-requests