Versions Compared

Version Old Version 1 New Version Current
Changes made by

Rajkumar Rajamanickam

Rajkumar Rajamanickam

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Directly upgrading from SCS 1.2 to SCS 1.3 is not supported, but this limitation is removed starting with SCS 1.4. Swarm supports upgrading from SCS 1.1, 1.2, or 1.3 to SCS 1.4 and booting from Storage bundle v15.0 with multicast disabled.

Upgrade Notes

...

Any version before SCS 1.4 cannot boot versions of Swarm storage that include the optional multicast feature (version 15.0 and later). This is due to changes required in SCS to support this feature.

Info

Important

This document is intended to provide upgrading steps for the latest SCS version for Rocky Linux 8 and above. If you are planning to migrate from CentOS 7 to Rocky Linux 8, refer to Migrating Swarm Components from CentOS 7 to Rocky Linux 8.

Upgrade Notes

  • Complete the SCS upgrade first if upgrading both SCS and Swarm Storage simultaneously. Then add the new Swarm Storage component to the SCS repo (using scsctl repo component add ...). During this process, scsctl will prompt as to whether or not to enable multicast for the storage cluster by asking to set a value for cip.multicastEnabled. Select True to enable the use of multicast (this matches the behavior of prior versions of Swarm), or False to disable it. If you are unsure which to choose, contact DataCore Support.

Refer to the following steps to upgrade SCS:

  1. If static IP addresses were previously assigned before this upgrade, skip this step and proceed to step#2.

  2. Allow DHCP to assign IP addresses
    When the cluster nodes are rebooted, DHCP will assign an IP address to each node. If the nodes have already been booted with manually assigned IPs, the assigned IP addresses will remain the same. If IP addresses were not manually assigned, but existing DHCP leases are still in effect, then currently assigned IP addresses will remain the same. If existing DHCP leases have expired (or this is the first boot of the storage cluster), DHCP will assign IP addresses from the allocated pool in no particular order, so proceed to “Boot/reboot” Swarm nodes.

    3. Pre-assign an IP address to each storage node
    In this case, an IP address must be manually assigned to each storage node before it is rebooted. The procedure for manual assignment is fully explained in Configuring Swarm for Static IPs with Swarm Cluster Services (SCS)).
    The summary of the manual assignment procedure is:

  3. Get an instance list that provides a node ID to use in the next step.

    Code Block
    scsctl storage instance list

    4. Assign an IP address to each node.

    Code Blockscsctl storage config set -d -i {chassis ID} "network.ipV4Address={your.static.address.here}"

    Disable the SELinux.

    1. Check if SELinux is enabled or disabled. In a default RL8 installation, it will be Enforcing. However, if it is already disabled, skip to step 2.

      Code Block
      getenforce

    2. Disable SELinux, by editing the /etc/selinux/config file, commenting out the line SELINUX=enforcing or SELINUX=permissive, and adding the line SELINUX=disabled. Then reboot the server after saving the file.

      Code Block
      vi /etc/selinux/config
...
#SELINUX=enforcing
SELINUX=disabled
...
reboot

  4. Install the new RPM.

Code Block
rpm -Uvh swarm-scs-[version].x86_64.rpm

  1. Run the following command.

Code Block
scsctl diagnostics upgrade_check

Note

Refer to the following step if an error occurs during the upgrade_check command:

Code Block
systemctl restart swarm-platform && sleep 90

  1. Run the diagnostics check.

    Code Block
    scsctl diagnostics config scan_missing

    It shows the below output:

    Code Block
    Running step [11/11]: Show the next steps after this wizard
  ********************************************************************************
  Congratulations, your Swarm Cluster Services server has been upgraded!
  Please reboot, then run the following to ensure your system is fully configured:

  2. Reboot the system.

  3. Re-initialize DHCP.

    Code Block
    scsctl init dhcp --dhcp-reserve-lower [integer]

  4. Choose the SCS version to activate the latest version.

    Code Block
    scsctl platform software activate
Info

Info

A customer might see the below error in the output while upgrading to SCS 1.7 or above, but this is safe to ignore it.

Code Block
Running step [4/11]: Re-enable systemd management of SCS Linux services
  Disabling service "swarm-platform.service" for pod "swarm-platform"...
  Failed to disable services: b'Failed to execute operation: No such file or directory\n'
  Deleting service file for pod "swarm-platform": /etc/systemd/system/swarm-platform.service [exists: False, symlink: True]
  Retry: Disabling service "swarm-platform.service" for pod "swarm-platform"...

We would need some additional necessary steps to upgrade directly from SCS 1.4 to 1.7.1 under the following conditions:

  • The current instance is using static IP assignments for storage nodes, using the node.cfg template method.

  • The storage cluster supported by the current instance is running a version of CAStor that does not support direct IP assignment, a version of CAStor that does not include the setting, “network.useStaticAddresses”.

Info

When the above conditions are absent, upgrading SCS and the storage software will go smoothly as described above.

When these conditions are true, the upgrade process requires additional steps:

  • After SCS is upgraded to 1.7.1, the storage software must be upgraded to the most recent version or any version that supports direct IP assignment and includes the “network.useStaticAddresses” setting.

  • After the new storage software version is activated, the storage cluster must be rebooted before any direct IP assignment is performed.

After these additional steps, the direct assignment of static IPs and the unsetting of the node.cfg templates can proceed as usual. The cluster gets rebooted again once that process is completed.

...