This issue is resolved in vRealize Log Insight 8.10.2 (build number 21145187)
Workaround:
To work around the issue:
- Download the Bootstrapper.tar.gz file attached to this article
- Using SCP software such as WinSCP or FileZilla, copy the file to the /tmp directory of the primary node
- SSH to the primary node as root
- Stop the Log Insight service
systemctl stop loginsight
- Change to this directory
cd /usr/lib/loginsight/application/3rd_party/apache-tomcat-8.5.82/webapps/ROOT/WEB-INF/classes/com/vmware/loginsight/web
- Backup the old files to the root directory
mv bootstrap ~/bootstrap_old
Note: This backup file can be removed after some time, once the cluster is confirmed to be healthy
- Make a new directory and navigate there
mkdir bootstrap && cd bootstrap
- Extract the Bootstrapper.tar.gz file
tar xzf /tmp/Bootstrapper.tar.gz
- Start the Log Insight service
systemctl start loginsight
Note: Wait several minutes to allow the service to come up, and then verify the availability of the primary node's UI
- Re-configure the vIDM Integration from Administration->Configuration->Authentication->VMware Identity Manager
- Restart the Log Insight service on the primary node once more, and verify the availability of the UI after several minutes
systemctl restart loginsight