SevOne Data Insight Upgrade Process Guide

About

This document allows you to upgrade SevOne Data Insight >= 3.5 to SevOne Data Insight 6.7.

IMPORTANT: PLEASE READ BEFORE CONTINUING...
The operating system changed in SevOne Data Insight 3.5 from Red Hat Enterprise Linux (RHEL) to CentOS 7. If you are on SevOne Data Insight >= 3.0.0 and SevOne Data Insight <= 3.4.1, please STOP.

Please refer to SevOne Data Insight Migrate Operating System & Data Guide on how to migrate the operating system and data before performing an upgrade.
Warning
SevOne Data Insight depends on SevOne NMS to generate the reports. It is very important that resource names in SevOne NMS that are being used by SevOne Data Insight are NOT changed. Changing the resource names will break the reports that are dependent on them.
Please do not run sevone-cli command from a subdirectory under /opt/SevOne/upgrade. It can be run from any directory except for from subdirectories under /opt/SevOne/upgrade.

For details on sevone-cli, please refer to SevOne Data Insight Troubleshooting / Debug / Tools Guide > section Tools > subsection SevOne CLI.
SevOne Data Insight deployed on IPv4 networks is compatible with SevOne NMS clusters running on Native IPv6 clusters.
IMPORTANT
If you have IPv6 enabled in your environment, please disable the MySQL metrics server before proceeding with the upgrade. Please refer to SevOne Data Insight Administration Guide > Configuration > Helm Chart > section Disable MySQL Metrics Server.
Terminology usage...
In this guide if there is,
  • [any reference to master] OR
  • [[if a CLI command (for NMS or Kubernetes or Redis) contains master] AND/OR
  •  [its output contains master]],
   it means leader or control plane.

And, if there is any reference to slave or worker, it means follower or agent.

Pre-Upgrade Checklist

Version Matrix

IMPORTANT
  • You must be on SevOne Data Insight version >= 3.5.
  • If you are on SevOne Data Insight 3.5.x and would like to upgrade to SevOne Data Insight 6.7, you must first upgrade to SevOne Data Insight 3.11.x followed by an upgrade to this version of SevOne Data Insight.
  • If you are on SevOne Data Insight 3.6.x or above, you may directly upgrade to this version of SevOne Data Insight.

The upgrade table below provides details whether your current start version of SevOne Data Insight supports a direct upgrade to your target SevOne Data Insight version. For example, if you are on SevOne Data Insight 3.5.x, you will first need to upgrade to SevOne Data Insight 3.11.x before upgrading to SevOne Data Insight 3.12.x or above.

Start Version Target Version
  3.5.x 3.6.x 3.7.x 3.8.x 3.9.x 3.10.x 3.11.x 3.12.x 3.13.x 3.14.x 6.5.x 6.6.x 6.7.x
3.4.x diCheck icon diCheck icon diCheck icon diCheck icon diCheck icon diCheck icon diCheck icon diCheck icon diCheck icon diError icon diError icon diError icon diError icon
3.5.x   diCheck icon diCheck icon diCheck icon diCheck icon diCheck icon diCheck icon diError icon diError icon diError icon diError icon diError icon diError icon
3.6.x     diCheck icon diCheck icon diCheck icon diCheck icon diCheck icon diCheck icon diCheck icon diCheck icon diError icon diError icon diError icon
3.7.x       diCheck icon diCheck icon diCheck icon diCheck icon diCheck icon diCheck icon diCheck icon diCheck icon diCheck icon diCheck icon
3.8.x         diCheck icon diCheck icon diCheck icon diCheck icon diCheck icon diCheck icon diCheck icon diCheck icon diCheck icon
3.9.x           diCheck icon diCheck icon diCheck icon diCheck icon diCheck icon diCheck icon diCheck icon diCheck icon
3.10.x             diCheck icon diCheck icon diCheck icon diCheck icon diCheck icon diCheck icon diCheck icon
3.11.x               diCheck icon diCheck icon diCheck icon diCheck icon diCheck icon diCheck icon
3.12.x                 diCheck icon diCheck icon diCheck icon diCheck icon diCheck icon
3.13.x                   diCheck icon diCheck icon diCheck icon diCheck icon
3.14.x                     diCheck icon diCheck icon diCheck icon
6.5.x                       diCheck icon diCheck icon
6.6.x                         diCheck icon

Obtain Required Files

IMPORTANT
Please execute all the pre-upgrade commands in this section based on SevOne Data Insight version you are on before performing an upgrade using the Command Line Interface or Graphical User Interface.
  1. Using ssh , log into SevOne Data Insight as sevone.

    $ ssh sevone@<SevOne Data Insight 'control plane' node IP address or hostname>

    Example: Currently on SevOne Data Insight 6.6 and to be upgraded to SevOne Data Insight 6.7

    $ ssh sevone@10.128.9.176
  2. Change directory to /opt/SevOne/upgrade.

    $ cd /opt/SevOne/upgrade
  3. Download the following (latest) files from IBM Passport Advantage (https://www.ibm.com/software/passportadvantage/pao_download_software.html) via Passport Advantage Online. However, if you are on a legacy / flexible SevOne contract and do not have access to IBM Passport Advantage but have an active Support contract, please contact IBM SevOne Support for the files. You must place these files in /opt/SevOne/upgrade directory of the control plane node.

    1. sdi-v6.7.0-build.160.tgz

    2. sdi-v6.7.0-build.160.tgz.sha256.txt

    3. signature-tools-<latest version>-build.<###>.tgz For example, signature-tools-2.0.1-build.1.tgz

    4. signature-tools-<latest version>-build.<###>.tgz.sha256.txtFor example, signature-tools-2.0.1-build.1.tgz.sha256.txt

      $ ls -lah /opt/SevOne/upgrade

      You should see all the files mentioned above in this directory.

      /opt/SevOne/upgrade/freight directory contains yum packages for air-gapped (no internet) environments.

Confirm SevOne Data Insight Version

Important: Prior to performing the upgrade to SevOne Data Insight 6.7, execute the steps below based on SevOne Data Insight version you currently are on.

for SevOne Data Insight 3.5 to 3.9

  1. Remove any possible conflicting packages left over from RHEL.

    $ ansible all --become -a "warn=false yum remove -y dracut-config-generic"
  2. Execute the following commands to verify the checksum of the code signing tool before extracting it.

    $ cd /opt/SevOne/upgrade
    
    $ cat $(ls -Art signature-tools-*.tgz.sha256.txt | \
    tail -n 1) | sha256sum --check
    
    $ sudo tar xvfz $(ls -Art /opt/SevOne/upgrade/signature-tools-*.tgz | \
    tail -n 1) -C /
    
    $ cd ~
  3. Verify the signature of SevOne Data Insight .tgz files.

    $ /usr/local/sbin/SevOne-validate-image \
    -i $(ls -Art /opt/SevOne/upgrade/sdi-*.tgz | tail -n 1) \
    -s $(ls -Art /opt/SevOne/upgrade/sdi-*.tgz.sha256.txt | \
    tail -n 1)
  4. Remove the old upgrade files (if any).

    $ find /opt/SevOne/upgrade -maxdepth 1 \
    -type d -not -name "upgrade" | xargs rm -rf
  5. Extract the latest SevOne Data Insight build files.

    $ tar xvf $(ls -Art /opt/SevOne/upgrade/sdi-*.tgz  | \
    tail -n 1) -C /opt/SevOne/upgrade/
  6. Check if sevone-cli is installed already.

    Example

    $ rpm -qa | grep sevone-cli
    sevone-cli-2.4.0-3.el7.x86_64

    The command above returning a version indicates that sevone-cli is installed.

    If sevone-cli is not installed, the command above will not return any version. And, you will need to execute the following command to install sevone-cli.

    $ sudo rpm -Uvh /opt/SevOne/upgrade/utilities/sevone-cli-*.rpm
  7. (optional) You may now install SOA on all peers.

    If a cluster is larger than ~20 peers, it is recommended that you only upgrade the datasource nms and schedule to run the upgrade on all peers at a later time.
    IMPORTANT
    When upgrading SOA, nginx service will restart on your SevOne NMS. This causes a very brief service impact.
    $ sevone-cli soa upgrade \
    /opt/SevOne/upgrade/utilities/SevOne-soa-*.rpm \
    --all-peers
  8. Run the pre-check playbook.

    $ ansible-playbook /opt/SevOne/upgrade/ansible/playbooks/precheck.yaml
  9. Validate that Internal Field Notices (IFNs) FN00068 and FN00070 have been applied on both the control plane and agent nodes.

    FN00068

    This issue is due to a bug with the CentOS kernel reporting incorrect memory usage. Due to this, Kubernetes does not schedule or restart any pods on the affected node because it thinks there is no memory remaining. To check if the IFN needs to be applied, execute the following command.

    $ cat /proc/cmdline | grep -qi 'cgroup.memory=nokmem' || \
    echo ">> IFN 68 NOT APPLIED"

    FN00070

    This issue only affects users who have been migrated over from RHEL (using the unrhel migration tool). To check if the IFN is applied, execute the following command.

    $ nmcli dev | grep -i ^eth && (cat /proc/cmdline | \
    grep -qi 'biosdevname=0 net.ifnames=0' || \
    echo ">> IFN 70 NOT APPLIED") || \
    echo ">> IFN 70 NOT NEEDED"
    Important: If FN00068 and/or FN00070 needs to be applied, please contact IBM SevOne Support for the IFN's patch instructions / workaround / solution.
  10. Ensure ports 3000 and 3001 are accessible from your browser. The following table lists the default port numbers and its respective config file location for the client and API.

    Name Default Port Config File Location
    Client 3000 /etc/sevone-guii/client.custom.yaml
    API 3001 /etc/sevone-guii/api.custom.yaml
Important: There is a 15-minute grace period to wrap up any lingering items. If they are unable to be completed in a timely manner, you will need to reschedule the upgrade.

for SevOne Data Insight >= 3.10

  1. Execute the following commands to verify the checksum of the code signing tool before extracting it.

    $ cd /opt/SevOne/upgrade
    
    $ cat $(ls -Art /opt/SevOne/upgrade/signature-tools-*.tgz.sha256.txt | \
    tail -n 1) | sha256sum --check
    
    $ sudo tar xvfz $(ls -Art /opt/SevOne/upgrade/signature-tools-*.tgz | \
    tail -n 1) -C /
    
    $ cd ~
  2. Verify the signature of SevOne Data Insight .tgz files.

    $ /usr/local/sbin/SevOne-validate-image \
    -i $(ls -Art /opt/SevOne/upgrade/sdi-*.tgz | tail -n 1) \
    -s $(ls -Art /opt/SevOne/upgrade/sdi-*.tgz.sha256.txt | tail -n 1)
  3. Remove old upgrade files, if any.

    $ find /opt/SevOne/upgrade -maxdepth 1 \
    -type d -not -name "upgrade" | xargs rm -rf
  4. Extract the latest SevOne Data Insight build files.

    $ tar xvf $(ls -Art /opt/SevOne/upgrade/sdi-*.tgz  | \
    tail -n 1) -C /opt/SevOne/upgrade/
  5. Check if sevone-cli is installed already.

    Example

    $ rpm -qa |grep sevone-cli
    sevone-cli-2.4.0-3.el7.x86_64

    The command above returning a version indicates that sevone-cli is installed.

    If sevone-cli is not installed, the command above will not return any version. And, you will need to execute the following command to install sevone-cli.

    $ sudo rpm -Uvh /opt/SevOne/upgrade/utilities/sevone-cli-*.rpm
  6. You may now install / upgrade SOA.

    IMPORTANT
    When upgrading SOA, nginx service will restart on your SevOne NMS. This causes a very brief service impact.
    SOA version
    SOA must be on the latest version on all appliances in SevOne NMS cluster. Command Line Interface (CLI) must be used to upgrade SOA on all peers as the graphical user interface (GUI) only upgrades SOA for the NMS appliance you are connected to.

    Execute the command to install / upgrade SOA only on the Cluster Master and HSA

    $ sevone-cli soa upgrade \
    /opt/SevOne/upgrade/utilities/SevOne-soa-*.rpm

    Execute the command to install / upgrade SOA on ALL peers in the cluster

    $ sevone-cli soa upgrade \
    /opt/SevOne/upgrade/utilities/SevOne-soa-*.rpm \
    --all-peers
  7. Run the pre-check playbook.

    $ sevone-cli playbook precheck
  8. Validate that Internal Field Notices (IFNs) FN00068 and FN00070 have been applied on both the control plane and agent nodes.

    FN00068

    This issue is due to a bug with the CentOS kernel reporting incorrect memory usage. Due to this, Kubernetes does not schedule or restart any pods on the affected node because it thinks there is no memory remaining. To check if the IFN needs to be applied, execute the following command.

    $ cat /proc/cmdline | grep -qi 'cgroup.memory=nokmem' || \
    echo ">> IFN 68 NOT APPLIED"

    FN00070

    This issue only affects users who have been migrated over from RHEL (using the unrhel migration tool). To check if the IFN is applied, execute the following command.

    $ nmcli dev | grep -i ^eth && (cat /proc/cmdline | \
    grep -qi 'biosdevname=0 net.ifnames=0' || \
    echo ">> IFN 70 NOT APPLIED") || \
    echo ">> IFN 70 NOT NEEDED"

    If IFN FN00068 and/or FN00070 is not applied, please execute the following command.

    $ sevone-cli playbook up --tags kernel

    Then, perform a restart of the machine.

    $ sudo reboot

    This can take ~5 - 10 minutes for Kubernetes to come up. To verify if Kubernetes is up and running, run the following commands.

    Example

    $ kubectl get nodes
    NAME        STATUS   ROLES                  AGE   VERSION
    sevonek8s   Ready    control-plane,master   52d   v1.28.2+k3s1

    $ kubectl get pods
    NAME                                                      READY   STATUS      RESTARTS        AGE
    di-create-secrets-xllfj                                   0/1     Completed   0               22h
    di-upgrade-l2cs8                                          0/1     Completed   0               22h
    clienttest-success-89lmt                                  0/1     Completed   0               22h
    clienttest-fail-lb8mq                                     0/1     Completed   0               22h
    di-report-version-sweeper-28276440-zpcxt                  0/1     Completed   0               20h
    ingress-ingress-nginx-controller-54dfdbc9cf-g9wdz         1/1     Running     0               22h
    di-prometheus-node-exporter-shnxk                         1/1     Running     0               22h
    di-graphql-7d88c8c7b5-fbwgc                               1/1     Running     0               22h
    di-ui-5b8fbcfc54-rtwlq                                    1/1     Running     0               22h
    di-kube-state-metrics-6f4fbc67cb-tsbbk                    1/1     Running     0               22h
    di-migrator-fdb9dd58b-29kl2                               2/2     Running     0               22h
    ingress-ingress-nginx-defaultbackend-69f644c9dc-7jvvs     1/1     Running     0               22h
    di-printer-7888679b59-cqp9q                               2/2     Running     0               22h
    di-scheduler-7845d64d57-bdsm2                             1/1     Running     0               22h
    di-registry-68c7bbc47b-45l5v                              1/1     Running     0               22h
    di-djinn-api-5b4bbb446b-prsjd                             1/1     Running     1 (22h ago)     22h
    di-mysql-0                                                2/2     Running     0               22h
    di-prometheus-server-7dc67cb6b5-bjzn5                     2/2     Running     0               22h
    di-redis-master-0                                         2/2     Running     0               22h
    di-wdkserver-6db95bb9c9-5w2kt                             2/2     Running     0               22h
    di-assetserver-5c4769bd8-6f2hw                            1/1     Running     0               22h
    di-prometheus-node-exporter-mp5xf                         1/1     Running     0               22h
    di-report-tombstone-sweeper-28277040-kj227                1/1     Running     0               10h
    datasource-operator-controller-manager-5cf6f7f675-h5lng   2/2     Running     3 (5h37m ago)   22h
    di-asset-sweeper-28277645-tq6gb                           0/1     Completed   0               12m
    di-user-sync-28277645-dl6ks                               0/1     Completed   0               12m
    di-asset-sweeper-28277650-hxwvn                           0/1     Completed   0               7m46s
    di-user-sync-28277650-6kxf7                               0/1     Completed   0               7m46s
    di-asset-sweeper-28277655-gjtpr                           0/1     Completed   0               2m46s
    di-user-sync-28277655-chgxd                               0/1     Completed   0               2m46s
  9. Ensure ports 3000 and 3001 are accessible from your browser. The following table lists the default port numbers and its respective config file location for the client and API.

    Name Default Port Config File Location
    Client 3000 /etc/sevone-guii/client.custom.yaml
    API 3001 /etc/sevone-guii/api.custom.yaml
There is a 15-minute grace period to wrap up any lingering items. If they are unable to be completed in a timely manner, you will need to reschedule the upgrade.

Confirm Minimum Specification Requirements

SevOne Data Insight now programmatically enforces the production specifications of of 8 vCPU cores / 32 GB RAM / 250 GB HDD.

Please refer to SevOne Data Insight Administration Guide > section Configuration > subsection Helm Chart > Resource Requests & Limits for details on configuring the resource limits or disabling this requirement.

Kubernetes Certificates

Kubernetes creates self-signed certificates to communicate with its API Server. It is possible for these certificates to expire before they are auto-rotated.

If you see the following error when running any kubectl commands, please renew your Kubernetes certificates before continuing with the installation process. For details, please refer to SevOne Data Insight Administration Guide > section Deployment > subsection Rotate Kubernetes Certificates.

$ kubectl get pods
Unable to connect to the server: x509: certificate has expired or is not yet valid

Configure Timeout

The upgrade duration increases alongside the number of pod replicas (particularly with GraphQL pods). By default, the upgrade times out after 5 minutes; after which the rollback begins. You must consider increasing the timeout by specifying a duration for the timeout setting under app_di.

Using a text editor of your choice, edit /etc/ansible/group_vars/all/di.yaml file to change the timeout variable under app_di and then, save it.

Configure Timeout

app_di:
  chart: di
  enabled: true
  name: di
  namespace: default
  timeout: 10m

Upgrade

Important:

Have you executed all the commands mentioned in section Pre-Upgrade Checklist based on the SevOne Data Insight version you are on?

If no, please go to section Pre-Upgrade Checklist first.

If yes, you may proceed to perform the upgrade using the Command Line Interface or Graphical User Interface.

Warning: If you are upgrading from SevOne Data Insight 3.7, 3.8, or 3.9, you may run into Stop k3s-server if upgrading to new version issue when running the playbook tasks. For details, please refer to SevOne Data Insight Troubleshooting / Debug / Tools Guide > section Troubleshooting > Install / Upgrade Failures > TASK [ Stop k3s-server if upgrading to new version ].
To upgrade SevOne Data Insight, you need to install sevone-cli, if not installed already.
Check if sevone-cli is installed...
Example
$ rpm -qa | grep sevone-cli <br /> <br />
sevone-cli-2.4.0-3.el7.x86_64

The command above returning a version indicates that sevone-cli is installed. If sevone-cli is not installed, the command above will not return any version and you will need to execute the steps below.

  1. Remove directory /opt/SevOne/upgrade/utilities.

    $ rm -rf /opt/SevOne/upgrade/utilities
  2. Extract the latest build.

    $ tar xvfz $(ls -Art /opt/SevOne/upgrade/sdi-*.tgz | tail -n 1) -C /opt/SevOne/upgrade/ ./utilities
  3. Install sevone-cli.

    $ sudo rpm -Uvh /opt/SevOne/upgrade/utilities/sevone-cli-*.rpm

Remove any possible conflicting packages left over from RHEL.

$ ansible all --become -a "warn=false yum remove -y dracut-config-generic"

Execute the following steps to upgrade SevOne Data Insight using Command Line Interface or Graphical User Interface.

IMPORTANT
Please make sure to connect your Data Insight to an NMS before upgrading using Command Line Interface or Graphical User Interface. For details, please refer to SevOne Data Insight Installation Guide > section Connect NMS.

using Command Line Interface

Execute the following command to update SOA (if required) and upgrade SevOne Data Insight. You must be in screen session to execute the upgrade command below.

Start 'screen' session

$ screen -S upgrade

When running the upgrade using the Command Line Interface, it validates the checksum, extracts the upgrade file, upgrades sevone-cli (if required), upgrades SOA, attempts to read NMS IP list from SevOne Data Insight database, and configures the SSH keys for the NMS being used as a datasource.

After the upgrade completes successfully, SevOne highly recommends a reboot to update the kernel as it does not update automatically. To reboot, execute command, sudo reboot.

Important: When you run the command below, you will be prompted to enter the password two times. At the first prompt, enter the password you would enter when you SSH to SevOne Data Insight as sevone. At the second prompt, enter the password you would enter when you SSH to SevOne NMS as root.

Update SevOne Data Insight without using the Graphical User Interface Installer

$ /usr/local/sbin/SevOne-validate-image \
-i $(ls -Art /opt/SevOne/upgrade/sdi-*.tgz | tail -n 1) \
-s $(ls -Art /opt/SevOne/upgrade/sdi-*.tgz.sha256.txt | tail -n 1) \
--installer sdi
Important: When running the command above, you may notice some text in RED in some of the playbooks. If it says ...ignoring after this text, it is a benign error and it can be ignored.

Wait for a few minutes before you launch SevOne Data Insight.

Using a web browser of your choice, enter your SevOne Data Insight IP address or hostname of the machine you have upgraded in the URL. You will notice that SevOne Data Insight is now on the upgraded version i.e., 6.7.0.

GUI Installer Launch After Upgrade

using Graphical User Interface

  1. Execute the following command to update SOA on all your datasources and configure the Graphical User Interface Installer. You must be in screen session to execute the upgrade command below.

    Start 'screen' session

    $ screen -S upgrade

    After the upgrade completes successfully, SevOne highly recommends a reboot to update the kernel as it does not update automatically.

    To reboot, execute the following command.

    $ sudo reboot

    Please wait for ~10-15 minutes for Kubernetes and other services to fully spin up.

    Update SevOne Data Insight using the Graphical User Interface Installer

    $ /usr/local/sbin/SevOne-validate-image \
    -i $(ls -Art /opt/SevOne/upgrade/sdi-*.tgz | tail -n 1) \
    -s $(ls -Art /opt/SevOne/upgrade/sdi-*.tgz.sha256.txt | tail -n 1) \
    --installer sdi-gui
    When running the command above, you may notice some text in RED in some of the playbooks. If it says ...ignoring after this text, it is a benign error and it can be ignored.

    Example: The command returns the following

    ╒══════════════════════════════════════════════════════════════╕
    │ SEVONE GUI INSTALLER                                         │
    ╞══════════════════════════════════════════════════════════════╡
    │ Please open https://10.128.9.176:3000 in your web browser to │
    │ access the GUI Installer.                                    │
    ├──────────────────────────────────────────────────────────────┤
    │ Your credentials are:                                        │
    │ - Username: admin                                            │
    │ - Password: cTq`R}x@D$                                       │
    ├──────────────────────────────────────────────────────────────┤
    │ If you ever lose your credentials, they're stored in:        │
    │ /etc/sevone-guii/creds                                       │
    ╘══════════════════════════════════════════════════════════════╛

    You are now ready to upgrade SevOne Data Insight using the Graphical User Interface Installer.

  2. Using a web browser of your choice, enter the URL returned above. For example, https://10.128.9.176:3000.

    GUI Installer Start
    You will also need the credentials (Username and Password) returned. These credentials are also stored in /etc/sevone-guii/creds file.

    Example

    $ cat /etc/sevone-guii/creds | jq
    {
     "password": "cTq`R}x@D$",
     "tokenSecret": "opuhryHOLvpjAfQfNgbtRcZdSxQwjWVw",
     "username": "admin"
    }
  3. Click Update Cluster to update SevOne Data Insight. For example, upgrade from SevOne Data Insight 6.6.0+139 to SevOne Data Insight 6.7.0+140.

  4. Enter the credentials returned to perform the Self-Service Upgrade. For example, Username: admin and Password: cTq`R}x@D$

    GUI Installer Credential
    To use the Graphical User Interface installer in dark theme, click GUI Install Dark Theme.png next to SevOne logo.

    For help on what each upgrade step does, click Help icon button in the upper-right corner.

    Important: All the screenshots below are based on the example being used to write this document. Your total number of tasks passed (ok), skipped, failed, ignored, unreachable, or unexecuted will vary based on your setup. The tasks failed must be addressed as ansible has not ignored them.
  5. The graphical user interface installer checks the Current Version and the Upgrade Available version. If the current version is older than the upgrade version available, you are now ready to continue to Pre-Upgrade.
    GUI Installer Check Versions
    Important: Example
    Current Version is on SevOne Data Insight 6.6.0+139.
    Upgrade Available version is SevOne Data Insight 6.7.0+140.
    Important: During the Self-Service Upgrade, if you experience network connectivity issue or the upgrade has been halted for any reason, the self-service upgrade will resume from the step where it left off after the issue is resolved. However, if you are at the Upgrade step and the self-service upgrade has been halted for any reason, self-service upgrade will show a message requesting you to contact SevOne Support.
    To resume with the Self-Service Upgrade, using a web browser of your choice, re-enter the URL the setup script has returned. For example, https://10.128.9.176:3000.
  6. Click Continue to Pre-Upgrade>button.
    GUI Installer Run Pre-Upgrade
  7. You are now ready to run the pre-upgrade. Click Run Pre-Upgrade button.
    Pre-Upgrade step runs various checks to ensure that SevOne Data Insight cluster is healthy before the upgrade. It takes backups of the database and creates a copy of the security keys.
    GUI Installer Pre-Upgrade Completed
    To view the logs for a task, click Eye icon for the task you need the details for. The pop-up has Copy to clipboard button which allows you to copy all the contents in the pop-up and paste it into a file.
  8. Click Continue button to upgrade SOA.
    SOA version
    SOA must be on the latest version on all appliances in SevOne NMS cluster. Command Line Interface (CLI) must be used to upgrade SOA on all peers as the graphical user interface (GUI) only upgrades SOA for the NMS appliance you are connected to.
    Add flag --all-peers if you want to install SOA on all peers in the cluster.
    
    $ sevone-cli soa upgrade \
    /opt/SevOne/upgrade/utilities/SevOne-soa-*.rpm \
    <enter SevOne NMS IP address> --all-peers
    
  9. You are now ready to upgrade SOA. Click Run Upgrade SOA button. This can take a few minutes to run.
    GUI Installer SOA Upgraded
  10. Click Continue button to configure Data Insight chart values, if required. This allows you to add ingress settings, or tune defaults for large deployments, in addition to verifying previously configured values. If you do not want to configure the chart values i.e., modify the ingress or GraphQL or printer or MySQL settings, click the Continue button to go to the next step to perform the upgrade.
    GUI Installer Configure
    1. From Configuration drop-down, choose a configuration file from the list. For example, the primary configuration file is di_custom_guii.yaml. If SevOne Data Insight has already been configured, you can select that configuration from the drop-down list to edit it. If multiple configuration files are present, the files will be applied in the alphabetical order.
      Primary Configuration
    2. Ingress
      1. Base Domain - a base domain is added to the end of every host. For example, .reporting.
      2. Base Path - allows SevOne Data Insight to host itself at an arbitrary subpath. This is useful to allow for some types and routing, or to have SevOne Data Insight act as a page of a larger whole.
        Important: This can be a regular expression. If it includes a capture group, you MUST change captureGroup as well.
      3. Capture Group - indicates which part of the path gets passed through nginx. By default, nginx passes everything after the first /. But, if you add a regex in the Base Path, Capture Group must be changed.
      4. Hosts - Click Host icon to add the host name(s) that SevOne Data Insight must respond to.
      5. TLS Secret Name - name of kubernetes secret that contains the TLS certificate and key. Please set this to datainsightcerts.
    3. GraphQL
      1. Replicas - contains the number of GraphQL pods to run. Increase this number if you have multiple agent nodes and several concurrent users. The maximum value allowed is 10.
      2. Environmental Variables
        • Auth Timeout - duration in seconds before an idle user times out. The default value is 3600. The maximum value allowed is 100,000.
        • Skip Report Migration Dry Run - enable check box if you want to skip the report migration dry run.
        • Skip Check Datasources - enable check box if you want to skip the step to check datasources.
    4. Printer
      1. Replicas - contains the number of printer pods to run. Increase this number for large amounts of scheduled reports.
    5. MySQL
      1. Primary
        • Extra Flags - additional flags to pass to MySQL when starting on the primary instance. Only maximum connections must be passed. Use example for exact formatting. For example, --max_connections=1000.
    6. Maps
      Warning: IMPORTANT: Missing / misconfigured tile server for Map mode
      The tile server for Map (geospatial) mode is missing or misconfigured in SevOne Data Insight 3.13.0 - 3.13.9, 3.14.0 - 3.14.6, 6.5.0 - 6.5.4, and 6.6.0. You must successfully perform an upgrade to SevOne Data Insight 6.7.0 or above and at this step, you are required to configure variables Tileserver and Attribution to obtain the proper tiles for the maps.
      Note: Failure to set variable Tileserver while performing an upgrade from SevOne Data Insight 3.13.0 - 3.13.9, 3.14.0 - 3.14.6, 6.5.0 - 6.5.4, and 6.6.0 to SevOne Data Insight 6.7.0 or above, will convert your current map in Maps mode to Canvas mode without the ability to switch back to Map mode until the tile server is provided.
      If the owner of the selected tile server requires to be given credit for the tiles being used, set variable Attribution. Text entered in variable Attribution will appear in the bottom right corner of each map.

      For further assistance, please contact SevOne Support Team or your Technical Account Manager to configure this properly.
      1. Tileserver - enter the tile server URL containing the token. For details on how to create a tile server URL, please refer to [SevOne Data Insight Administration Guide](https://www.ibm.com/docs/en/sevone-npm/6.7?topic=operations-sevone-data-insight-administration-guide) < Configuration < Helm Chart < Configure Maps < section Create Tile Server URL.
        • for Dark mode, https://api.mapbox.com/styles/v1/sevone/cllfjv99c01mp01ql9neoau07/tiles/256/{z}/{x}/{y}@2x?access_token=<ACCESS_TOKEN>
        • for Light mode, https://api.mapbox.com/styles/v1/sevone/cllfl73f101qb01qnc7wh22i5/tiles/256/{z}/{x}/{y}@2x?access_token=<ACCESS_TOKEN>
      2. Attribution - enter some attribution; props to stamen for providing tiles, etc.
  11. Click Save. Configuration is saved in /opt/SevOne/chartconfs/di_custom_guii.yaml.
    Important: Once the configuration is saved, click Continue button to upgrade.
  12. You are now at the Upgrade step.
    Run Upgrade
  13. Click Run Upgrade button to run the upgrade.
    Important: Allows you to start the upgrade and show the progress. This can take a few minutes to run.
    Upgrade Completed

    SevOne Data Insight upgrade has now completed.
    Note: The task list can be long. Search tasks capability is available to search for text you are looking for in the task list.
    Note: To view the logs for a task, click Eye icon for the task you need the details for. The pop-up has Copy to clipboard button which allows you to copy all the contents in the pop-up and paste it into a file.
  14. Click the Continue button.
    Upgrade Finished
    Important: This indicates that the upgrade has completed successfully.
  15. You may now link the link Click Here.
  16. Link Click Here will launch SevOne Data Insight. You will notice that SevOne Data Insight is now on the upgraded version i.e., 6.7.0.
    Launch SevOne Data Insight After Upgrade
Example: Upgrade not required
If you are already on the version you are trying to upgrade to, you will get the You can proceed with redeploy/install message. This allows you to upgrade to a later version, if available.
Reploy or Install

Important: Additional details on GUI Installer can be found in SevOne Data Insight Administration Guide > Tools > section GUI Installer.
Note: Please refer to SevOne Data Insight Administration Guide for configuration and deployment details and SevOne Data Insight Troubleshooting / Debug / Tools Guide for troubleshooting scenarios, how to debug SevOne Data Insight, and various tools available.