Verifying Sisense Installation Completion - Analyzing Migration Pod Messages
Title: Verifying Sisense Installation Completion - Analyzing Migration Pod Messages
Summary
This article provides basic understanding of how to perform initial verification of installation/upgrade process.
Specifically, it covers the flow related to the "migration" pod and the "provisioner" pod, and provides steps to analyze if installation/upgrade process was successful.
Main Content
Step-by-Step Instructions to verify and confirm installation/upgrade is completed
1. Verify Upgrade Completion:
- Ensure that the upgrade process has completed successfully by checking the status of all Sisense pods.
- Use the following command to describe the pods in the sisense (default namespace for Sisense; in case another namespace is used for the installation, replace sisense with the actual one) namespace:
kubectl -n sisense describe pod
helm ls -A
- Verify that all Sisense containers are using the desired major version and that the provisioner pod is in the "Completed" state.
- Verify that “sisense-<desired_version>” Helm chart is in “deployed” state
NOTE: If case of initial installation, some pods might be in Init status - this is expected behavior due to the need of license activation. Check if Sisense can be accessible by visiting <your_Sisense_URL>/app/account#/login page
2. Check Migration Pod Possible Errors:
- Review the output of the migration pod to identify any errors.
- Note that the migration process includes a set of verifications. If a critical issue is detected, the process will crash and exit with code ‘1’. However, if the process exits with code '0', it indicates a successful run despite any informational errors.
kubectl -n sisense logs $(kubectl -n sisense get pod -l app.kubernetes.io/name=migration --no-headers | head -n 1 | awk '{print $1}')
- Common errors may include, for example, verification issues with cleaning dashboard subscriptions, where an argument might be null instead of an expected integer. These errors are informational and do not indicate a migration failure.
3. Understanding Provisioner Process:
- The provisioner process may complete faster than usual for newer Sisense releases (such as L2024.3 and higher) due to backend optimizations.
- If the provisioner pod freezes or ends without completion, please contact Sisense Support Team.
- If Provisioner pod is in “Completed” status it usually indicates to successful installation/upgrade completion
Related Content:
Docs: https://docs.sisense.com/main/SisenseLinux/installing-sisense-on-linux.htm
Academy: https://academy.sisense.com/linux-essentials-for-ms
