VMware Aria Operations for Logs 8.14 Hot Fix 1 is a public Hot Fix that addresses the following issues:
Cassandra seed IP is resolved to 127.0.0.1.
[Change] Disabled hot reloading network configuration from vApp Properties during VM reboot.
Manual edit of the /etc/systemd/network/10-eth0.network file is required to make network changes after initial deployment.
Keytool was used to extract and preserve certificate on upgrade. On 8.14 keytool-no-provider was added, but since the tool was not available on 8.12.x, we ended up with an empty certificate file.
With FIPS mode enabled, custom certificate was not properly applied due to cassandra using X.509 as both key and trust algorithm.
When joining a new node, cacert.pem (cqlsh truststore) was not correctly created if cluster had custom certificate applied, as at the point of it's creation cassandra config directory was still missing.
Environment
VMware Aria Operations for Logs 8.14.x
Resolution
Download and install the correct Hot Fix version that matches your version of VMware Aria Operations for Logs.
Download the VMware Aria Operations for Logs 8.14 Hot Fix PAK file from the Broadcom Support Portal.
Note: Select VMware Aria Operations for Logs as the Product and select 8.14 as the version and click Search.
Select the option below.
Release Name
Release Date
Build Number
File Name
vRLI-8.14-HF1
11/13/2023
22757387
VMware-vRealize-Log-Insight-8.14.0-22757387.pak
Prerequisites
Create a snapshot or backup copy of the VMware Aria Operations for Logs virtual appliance(s)
Obtain a copy of the VMware Aria Operations for Logs upgrade bundle .pak file for the release you are upgrading to
Note: The VMware Aria Operations for Logs 8.14 HF1 pak file can be used to upgrade to 8.14 HF1 from 8.12.
Verify that you are logged in to the VMware Aria Operations for Logs web user interface as a user with the Edit Admin permission. The URL format is https://log-insight-host, where log-insight-host is the IP address or host name of the primary node of the VMware Aria Operations for Logs virtual cluster.
Make a note of any nodes you are upgrading that are in maintenance mode. When the upgrade is finished, you must move them from the state Connected to Maintenance mode.
Procedure
Click the configuration drop-down menu icon and select Administration.
Under Management, click Cluster.
Click Upgrade from PAK to upload the .pak file.
Accept the new EULA to complete the upgrade procedure.
What to do next
After the primary node upgrade process is complete, you can view the remaining upgrade process, which is automatic.
Check for the email sent to the Admin to confirm the upgrade completed successfully.
After upgrade, all nodes are brought online even if they were in maintenance mode before the upgrade. Move these nodes back to maintenance mode as needed.
Remove the snapshots from the VMware Aria Operations for Logs appliance(s) within ~72 hours after a successful upgrade to avoid performance issues