Swarm Cluster Services 1.7.4 Release Notes
Changes in Swarm Cluster Services (SCS) 1.7.4
This release introduces the following improvements and updates:
Support for Enterprise Linux 9: SCS 1.7.4 is supported exclusively on EL9-based operating systems, including Rocky Linux 9 and Red Hat Enterprise Linux 9. Earlier versions of Enterprise Linux (EL8 and earlier) are not supported. This update also includes improved log rotation capabilities. (SCSL-457)
Known Issues
SCS 1.7.4 on RL9 Blocks Outbound Traffic: Swarm Component Server (SCS) 1.7.4 on Rocky Linux 9 may block outbound traffic by default due to missing firewalld ingress/egress zone definitions. This can cause broken replication, missing health reports, and reduced support visibility. Refer to the KB article Enable Firewall Zone Forwarding on Rocky Linux 9 for firewalld configuration and backend interface updates. (OEM-140)
Limitations
No Direct Upgrade Path: Due to operating system upgrade constraints, a direct upgrade to SCS 1.7.4 is not supported. Migration requires backing up the existing SCS instance and restoring it on a system running SCS 1.7.4. Refer to the SCS Administration section on Backup and Restore.
Cluster Expansion Requirements: When adding new storage nodes to a cluster, ensure all existing nodes are online to avoid potential IP address conflicts during the boot sequence. (SCSL-430)
Component Version Validation After Restore: After restoring from a backup, verify and update the activated versions of installed components as necessary. (SCSL-425)
System Reset Post-Upgrade: Performing a system reset (
scsctl system reset) immediately after an upgrade may result in an error. If this occurs, contact DataCore Support for assistance. (SCSL-370)SELinux Compatibility: SELinux must be disabled before initializing or upgrading SCS. (SCSL-365)