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:
Migrate a Splunk SOAR (On-premises) install from RHEL 7 or CentOS 7 to RHEL 8
Support for Red Hat Enterprise Linux 8 (RHEL) was added with the release of version 5.5.0. This topic provides a high-level overview of the process for migrating your host's operating system to RHEL 8.
This article focuses on the current Splunk SOAR (On-premises) release. You can upgrade to any Splunk SOAR (On-premises) release 5.5.0 or higher.
Before you begin
Before you migrate your deployment from RHEL 7 or CentOS 7 to RHEL 8, make a full backup of of your current release deployment. See Splunk SOAR (On-premises) backup and restore overview.
It is safe to restore a RHEL 7 Splunk SOAR (On-premises) backup on RHEL 8.
Now migrate your operating system using one of these methods:
- Upgrade the operating system in place on the host. See Upgrade the Splunk SOAR (On-premises) host operating system in place.
- Upgrade the operating system on a new host, use backup and restore to transfer your information to the new host. See See Upgrade the Splunk SOAR (On-premises) to a new RHEL 8 host by using backup and restore.
Upgrade the Splunk SOAR (On-premises) host operating system in place
This method converts and upgrades the operating system on your deployment in place.
Operating system migrations paths:
- RHEL 7 upgrade to RHEL 8
- CentOS 7 convert to RHEL 7, then upgrade to RHEL 8
Convert CentOS 7 to RHEL 7
Before your CentOS 7 operating system can be upgraded to RHEL 8, you must convert it to RHEL 7.
Follow Red Hat's instructions for converting CentOS 7 to RHEL 7. See Converting CentOS Linux to Red Hat Enterprise Linux on the Red Hat site.
Upgrade from RHEL 7 to RHEL 8
Follow Red Hat's instructions for upgrading RHEL 7 to RHEL 8. See the Upgrading from RHEL 7 to RHEL 8 on the Red Hat site.
Upgrade to the latest version of
Once you have upgraded the operating system on your deployment in place, upgrade to the current release. See Splunk SOAR (On-premises) upgrade overview and prerequisites.
Upgrade the Splunk SOAR (On-premises) host operating system for a cluster in place
This method converts and upgrades the operating system on your deployment for clusters in place. Before you begin, ensure that all cluster nodes are using a version 5.5.0 or higher.
- Upgrade the cluster nodes, one at a time.
If you are upgrading from CentOS 7, deactivate cron jobs for the duration of the upgrade.
- Upgrade to the current release. See Splunk SOAR (On-premises) upgrade overview and prerequisites.
Upgrade the Splunk SOAR (On-premises) to a new RHEL 8 host by using backup and restore
This method involves creating a new RHEL 8 system for your and restoring your existing to the new host.
Operating system migrations paths:
- RHEL 7 upgrade to RHEL 8
- CentOS 7 to RHEL 8
Do the following tasks.
- Delete all libssl* and libcrypto* files from the directory <$PHANTOM_HOME>/usr/lib64.
These libraries are provided by the operating system in RHEL 8. Deleting the copies in the SOAR distribution prevents conflicts, making the original RHEL 7 installation RHEL 8 compatible.
cd /opt/phantom/usr/lib64 rm libssl* rm libcrypto*
- If you have not already done so, upgrade your current deployment to the current release. See Splunk SOAR (On-premises) upgrade overview and prerequisites.
- After your upgrade to the current release is complete, make a full backup of of your current release deployment. See Back up a Splunk SOAR (On-premises) deployment.
- Create a new instance of the current where the operating system is RHEL 8. See
- Use the backup created earlier to restore the original deployment to the new deployment. See Restore Splunk SOAR (On-premises) from a backup.
Upgrade a Splunk SOAR (On-premises) cluster | Migrate from Splunk SOAR (On-premises) to Splunk SOAR (Cloud) |
This documentation applies to the following versions of Splunk® SOAR (On-premises): 6.0.2, 6.1.0, 6.1.1, 6.2.0, 6.2.1, 6.2.2, 6.3.0
Feedback submitted, thanks!