Checking before updating

Before you perform an update of your Turbonomic instance, you should run the upgrade-precheck.sh script. This script inspects your installation to check for the following:

  • Free disk space is sufficient.

    For example, the /var partition must be at least 340 GB in size. This is the recommended size for deployments starting in version 8.9.1. If you need to free up disk space to increase the size of the partition, you can delete old images that are not in use. For more information, see Increasing Available Disk Space.

  • (For online updates) The required endpoints can be accessed.

  • The MariaDB service is running.

    This check is for the default installation of the MariaDB service only. The script does not check an external installation of MySQL or MariaDB. If you deployed an external historical database, the script indicates that your MariaDB service is not running. This is a normal result.

  • The Kubernetes service is running.

  • The necessary Kubernetes certificates are valid.

    If the certificates are not valid, you can correct the issue by running a script located on your installation.

    • For VM images based on Rocky Linux, use /opt/local/bin/k8s-certs-renew.sh.

    • For VM images based on CentOS Linux, use /opt/local/bin/kubeNodeCertUpdate.sh.

    Important:

    • The k8s-certs-renew.sh script is not designed for CentOS Linux distributions and might cause serious errors if it is run on CentOS VMs. If you are running CentOS Linux, you must run the kubeNodeCertUpdate.sh script, regardless of your Turbonomic version level.

    • If you are running CentOS Linux with Turbonomic version 8.12.2 or later, the kubeNodeCertUpdate.sh script is in a versioned bin-* folder in the /opt/local/ directory. The version of the bin-* folder corresponds to the last version you ran before upgrading to 8.12.2 or later. For example, if you upgraded from 8.12.0 to 8.13.0, the script is located in the /opt/local/bin-8.12.0/ directory.

    • Before you run either script, save a snapshot of your current Turbonomic VM. This provides a reliable restore point you can turn to in the event that trouble occurs during the update.

      Before updating, shut down (not power off) the Turbonomic VM.

      sudo init 0

      Then, perform a snapshot (or clone the VM). After you have the snapshot, bring the VM back online and run the appropriate script for your Linux distribution.

  • Root password is not set to expire.

  • Time sync is enabled and current (if running).

  • All Turbonomic pods are running.

To run this script:

  1. Open an SSH terminal session to your Turbonomic instance.

    Log in with the System Administrator that you set up when you installed Turbonomic:

    • Username: turbo

    • Password: [your_private_password]

  2. Change to the scripts directory.

    cd /opt/local/bin
    /opt/local/bin/upgrade-precheck.sh

  3. Make the script executable.

    chmod +x upgrade-precheck.sh

  4. Run the script.

    ./upgrade-precheck.sh

    As the script executes, it identifies any issues that you should address before you run an update.