"Failed validating Kuberenetes ports at node" error while Sisense installation
Sometimes, while Sisense is being installed/re-installed on a Linux environment,
"Failed validating Kuberenetes ports at node" error might reveal.
Example of the error populated in sisense-installer.log:
=====
[2025-02-21 15:25:11] [0;31m** Failed validating Kuberenetes ports at node node1 (Internal IP: 10.48.39.136). **[0m
[2025-02-21 15:25:11]
[2025-02-21 15:25:11] ** Sisense validations failed. **
[2025-02-21 15:25:11] Errors from host 10.48.39.136:
Warning: Permanently added '10.48.39.136' (ECDSA) to the list of known hosts.
[2025-02-21 15:25:11] [0;31m** The following ports are not opened: **[0m
- 6443
- 10250
- 10248
- 10249
- 10256
- 10257
- 10259
[2025-02-21 15:25:11] [0;31m** Failed validating Kuberenetes ports at node node1 (Internal IP: 10.48.39.136). **[0m
[2025-02-21 15:25:11] ** Error occurred during Sisense validations section **
[2025-02-21 15:25:11] ** Exiting Installation ... **
=====
Such error usually means either ports are indeed not opened or installation is being performed
on the environment that already had Sisense in the past and some docker containers are still
present thus using the ports required.
NOTE! - The steps below should not be performed on existing Sisense deployment
since it might break the application.
In order to resolve it:
- Check if Docker containers are still present with the command below (in case
of multi-node run the command on each node):
docker ps -a
- Remove unwanted containers (in case of multi-node run the command on each
node):
docker container rm <container_id>
- NOTE! - You can remove all Docker containers at once, however, please first
make sure you are not running any non-Sisense containers in Docker:
docker container rm -f $(docker ps -a | tail -n +2 | awk '{print $1}')
- Run the installation again
Disclaimer: This post outlines a potential custom workaround for a specific use case or provides
instructions regarding a specific task. The solution may not work in all scenarios or Sisense versions, so we strongly recommend testing it in your environment before deployment. If you need further assistance with this please let us know.
