Changes in Swarm Cluster Services (SCS) 1.7.5

This release introduces the following improvements and updates:

Enhancements and Improvements

• Diagnostics Report Command: Introduced the scsctl diagnostics report command, which allows you to generate comprehensive system diagnostic reports. These reports include container health, log excerpts, DHCP configuration, firewall rules, network interfaces, component versions, system settings, and template overrides. (SCSL-310)

• Improved External Interface Detection: Enhanced network interface detection to ensure the correct interface is identified in environments with multiple network interfaces. (SCSL-388)

• Hardened Node Discovery: Node discovery now includes TCP reachability checks, improving cluster membership detection reliability, particularly in environments where multicast is disabled. (SCSL-397)

• Improved CLI Guidance for Cluster Configuration: Updated CLI prompts to clearly indicate that the group name must be specified using the cluster name in fully qualified domain name (FQDN) format. (SCSL-383)

• API Startup Timeout: Added support for a user-configurable timeout for requests issued during the API container startup sequence. (SCSL-460)

Issues Resolved

• UEFI Boot Mode Support: Fixed an issue that could prevent nodes from booting successfully in UEFI mode on Dell PowerEdge R760xs servers. (SCSL-472)

• Firewall Zone Configuration: Fixed an issue where firewall zone configuration could prevent proper traffic forwarding. Network communication now functions correctly on Rocky Linux 9 systems. (SCSL-487, OEM-140)

• Internal Network Default Route: Fixed an issue where the internal network adapter retained a default route after initialization, which could cause routing conflicts with the external network adapter. The initialization process now automatically disables the default route on the internal adapter. (SCSL-486)

• Bonded Network Interface Support During Initialization: Fixed an issue where bonded network interfaces on the internal network were not correctly supported during SCS initialization. (SCSL-240)

• Swarm Version Rollback: Fixed an issue that could prevent rollback to earlier Swarm storage versions when certain configuration settings were missing. Rollback operations now complete successfully. (SCSL-307)

• Log Rotation Configuration Correction: Corrected the log rotate configuration to properly reference the /var/log/datacore directory. (SCSL-237)

• Static IP Assignment During Migration: Fixed an issue where storage nodes could receive incorrect IP addresses when deploying a new SCS instance with a fresh etcd database connected to an existing cluster. (SCSL-488)

• Migration Stability Improvements: Fixed an issue where the Rocky Linux 8 to Rocky Linux 9 migration process could fail due to insufficient timeout when stopping Swarm Cluster Services pods. Timeout handling has been improved to ensure reliable migration. (SCSL-489)

• Subnet Mask Validation During Initialization: Fixed an issue where initialization incorrectly reported an error when specifying a netmask smaller than /24. Subnet masks such as /25, /26, /27, and /28 are now accepted without displaying a spurious error message. (SCSL-450)

Known Issues and Limitations

• Rocky Linux 9 Requirement: This release supports deployment on Rocky Linux 9 only. Systems running earlier Rocky Linux 8–based versions must complete the Rocky Linux 8 to Rocky Linux 9 migration process before upgrading. Upgrading from SCS version 1.7.4 to 1.7.5 follows the standard upgrade process.

• Cluster Expansion Requirements: When adding new storage nodes to a cluster, ensure that 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)