When you attempt a new installation of SAS® Visual Investigator 10.8 Hot Fix 17 or Hot Fix 18 or upgrade an existing SAS Visual Investigator 10.8 installation from an earlier Hot Fix version to Hot Fix 17 or Hot Fix 18, the deployment fails on the TASK [elasticsearchsecure-x64_redhat_linux_6-yum : Execute opensearch_check_cluster_status] with the following error and return code:
[ERROR] /opt/sas/viya/home/share/elasticsearch-secure/svi-opensearch-cluster-status.sh exited with return code 1
The sas-opensearch.log also displays the following warning message:
[2026-07-16T05:56:54,569][WARN ][o.o.d.HandshakingTransportAddressConnector] [<hostname>] handshake failed for [connectToRemoteMasterNode[<IP address>:9300]]
org.opensearch.transport.RemoteTransportException: [hostname][<IP address>:9300][internal:transport/handshake]
Caused by: org.opensearch.OpenSearchException: Node presenting certificate with SSL Principal {CN=<hostname>-client} could not securely connect to the cluster. Please ensure the principal is correct and present in the nodes_dn list.
This error occurs due to a space indention issue in the Hot Fix 17 and Hot Fix 18 versions of the OpenSearch installation script, svi-opensearch-setup.sh.
To circumvent the issue, complete the following steps on each OpenSearch host of the deployment. If you have multiple OpenSearch hosts, complete these steps on each host:
1. Stop the sas-viya-svi-elasticsearch-default service.
2. Ensure that there are no orphaned or stale OpenSearch processes lingering by running the following commands. Note: Ports 9200 and 9300 are the default OpenSearch ports. If you use different ports, replace 9200 and 9300 in the following commands with the correct ports.
ps wwuax | grep opensearch
sudo lsof -nP -i:9200
sudo lsof -nP -i:9300
If the commands return any processes, note their process IDs and kill them with the following command:
kill -9 <process-ID>
3. Back up your current /opt/sas/viya/home/share/elasticsearch-secure/svi-opensearch-setup.sh file. Rename the file to "svi-opensearch-setup_original.sh".
4. Download the svi-opensearch-setup.sh, which contains the correct space indention.
5. Copy svi-opensearch-setup.sh over to the /opt/sas/viya/home/share/elasticsearch-secure directory and make sure it is named svi-opensearch-setup.sh.
6. Ensure that the "sas" account owns the file and has Read, Write, and Execute permissions.
7. Start the sas-viya-svi-elasticsearch-default service backup.
After completing these steps, reattempt the installation or hot fix update or upgrade.
Note: A hot fix is planned to address the space indention issue.