After the future removal of the classic playbook editor, your existing classic playbooks will continue to run, However, you will no longer be able to visualize or modify existing classic playbooks.
For details, see:
Upgrade a single unprivileged instance
It is now possible to upgrade directly to later releases of Splunk SOAR (On-premises).
Privileged deployments upgrade directly to Splunk SOAR (On-premises) release 5.3.6, convert to unprivileged, then immediately upgrade to Splunk SOAR (On-premises) release 6.1.1.
Unprivileged deployments upgrade directly to Splunk SOAR (On-premises) release 6.1.1
See Splunk SOAR (On-premises) upgrade overview and prerequisites for more information.
Follow these steps to upgrade your unprivileged instance, or to convert and upgrade your existing, privileged instance to an unprivileged instance. Use these steps even if your unprivileged instance has limited access to the internet. The installation TAR file contains everything needed to complete this upgrade.
The same TAR file is used for install and upgrade processes. The file detects the presence of SOAR and installs or upgrades accordingly.
- Read upgrade overview and prerequisites.
- Restart the operating system if you did not recently restart it as part of the prerequisites in Step 1.
This step is required to ensure that the upgrade completes successfully and efficiently.
As the root user:reboot
- After the system restarts, log in to the operating system as the user that owns Splunk SOAR (On-premises). Do not perform the upgrade as the root user.
- Download the unprivileged installer from the Splunk SOAR site. The unprivileged installer prepackages its dependencies and can be installed on systems that cannot reach out to the internet.
The unprivileged installer is named in the formatsplunk_soar-unpriv-<major>.<minor>.<patch>.<build>-<commit_short_sha>-<os>-x86_64.tgz
. - Conditional: If you have previously upgraded this instance of Splunk SOAR (On-premises), you may still have a directory at <$PHANTOM_HOME>/splunk-soar. If that is true, remove that directory.
rm -rf <$PHANTOM_HOME>/splunk-soar
- Conditional: If this instance of Splunk SOAR (On-premises) is installed on RHEL 8.x, and you have previously tried to upgrade it with the installer for RHEL 7.x then the directory <$PHANTOM_HOME>/usr/lib64 must be removed.
rm -fr <$PHANTOM_HOME>/usr/lib64
Do not do this step if you are installing Splunk SOAR (On-premises) on RHEL 7.x
- Extract the TAR file you downloaded into the Splunk SOAR (On-premises) installation directory. This creates a new directory in the Splunk SOAR (On-premises) home directory, <$PHANTOM_HOME>/splunk-soar.
tar -xvf <installer>.tgz -C <$PHANTOM_HOME>
- Make sure that that your current installation of is running.
<$PHANTOM_HOME>/bin start_phantom.sh
- Change directory to the <$PHANTOM_HOME>/splunk-soar directory.
cd <$PHANTOM_HOME>/splunk-soar
- The installer package you extracted creates a file called soar-install in the <PHANTOM_HOME>/splunk-soar directory. Run that script:
./soar-install --upgrade --with-apps
- Conditional: If you extracted the installation TAR file to a different directory than <$PHANTOM_HOME>/splunk-soar, you must supply the path to your Splunk SOAR (On-premises) installation to the installation script.
<path/to/extracted/TAR file>/soar-install --splunk-soar-home <path/to/$PHANTOM_HOME> --upgrade --with-apps
You can see the full list of arguments for the soar-install script by using the
--help
option.
- Conditional: If you extracted the installation TAR file to a different directory than <$PHANTOM_HOME>/splunk-soar, you must supply the path to your Splunk SOAR (On-premises) installation to the installation script.
- After the upgrade is complete, remove installation package by deleting the <$PHANTOM_HOME>/splunk-soar directory.
rm -rf <$PHANTOM_HOME>/splunk-soar
Upgrade a single privileged instance | Upgrade a privileged cluster |
This documentation applies to the following versions of Splunk® SOAR (On-premises): 5.3.4
Feedback submitted, thanks!