Version Change Notes

This document records important notes and caveats for upgrading across versions. Read it carefully before you perform an upgrade.

tip

1. Upgrades involve changes across multiple versions. First, obtain your currently deployed version. Then read the notes below carefully. Intermediate versions must also be considered. For example, if you are currently on 24.05 and plan to upgrade to 24.11, read the change notes for 24.05 and all subsequent versions up to 24.11.
2. In this document, "this version" refers to the version selected in the top-right version selector.

24.05

Release date: 2024-06-01

Cluster management

• Load thresholds: In this version, Fsched changed how load thresholds are implemented, providing a more stable management experience. If your cluster relies on load thresholds, make sure to upgrade Fsched before upgrading the platform, otherwise the cluster configuration may become abnormal. If you cannot upgrade immediately, consider disabling this feature temporarily.

Environment configuration

• Notification configuration changes:
  Notification settings were optimized. SMTP port configuration is now split into SSL and non-SSL options.
  After the upgrade, the system will use the SSL port you configured in the old version to enable SMTP SSL. Confirm that the previously configured port is correct.
  To review the configuration, log in as the configuration admin and open the notification settings tab.
  

24.08

Release date: 2024-09-15

Cluster management

• Partition admin: A new partition-admin feature was introduced. This requires new Fsched configuration. If you upgrade the platform while using an older Fsched that does not have this configuration, cluster configuration may become abnormal. Make sure to upgrade Fsched before upgrading the platform. This feature cannot be disabled temporarily.

Desktop management

• Desktop applications: Desktop Applications were introduced in this version. This feature requires installing Web Portal related components and upgrading services. Install the following base components on desktop nodes:
  

  For Ubuntu:

  sudo apt install xdotool

  For CentOS:

  sudo yum install xorg-x11-utils xdotool

User management

• User expiration time: User expiration times configured before the upgrade will no longer take effect after the upgrade.
• Admin user behavior changes: In environments using the built-in user authentication system, the admin user no longer has remote connection and new task creation capabilities.
  Before upgrading, make sure to disconnect any remote sessions created by admin, otherwise they may keep consuming resources after the upgrade.

24.11

Release date: 2024-12-13

Environment configuration

• In Core-HA scenarios, if NTP server addresses were never configured in your 24.11 environment, make sure to configure them first and then perform the upgrade.

Operations

• Cluster analytics: Configure Grafana dashboards for cluster analytics.
  • If dashboards were customized before the upgrade: adjust cluster-monitor-panel.json as needed. See Customize the Cluster Analytics Grafana Dashboard.
  • If dashboards were not customized before the upgrade: delete the following file on the Core node (and also on the secondary Core node in Core-HA scenarios):

    sudo rm -rf /fastone-services/fastone/ui/assets/custom-data/cluster-monitor-panel.json

25.02

Release date: 2025-03-14

Remote access

• VNC remote access:
  • Before upgrading, upgrade the fastone-remote-access component on desktop nodes or cluster login nodes. Otherwise, after a login node reboot, VNC sessions cannot be automatically rebuilt from the database.
  • If you hit this issue, you can manually replace /opt/fastone-images/fastone-remote-access.sif on the login node with /opt/components/fastone-remote-access.sif from the Core node, then run sudo supervisorctl restart fastone-remote-access on the login node.

CWL tasks

• Task details:
  • The vali component on 25.02 head nodes is incompatible with the 25.05 environment. Remove the node from the cluster and upgrade it in Host Management, otherwise clicking CWL task details in the UI may fail.
  • If you hit this issue, manually replace /usr/bin/vali on the head node with /opt/components/vali-linux-amd64 from the Core node (in the 25.05 environment), add execute permission, then run sudo supervisorctl restart vali on the head node.

Direct tasks

• Task management: Task List may occasionally show incorrect start/end times. Upgrade the Core version to 25.05, remove the node from the cluster, then upgrade the node in Host Management.

25.05

Release date: 2025-05-30

Direct tasks

• Task management:

  • In 25.08, CPU/GPU display was added for tasks. Upgrade nodes in Host Management, otherwise CPU/GPU fields in Task List may be empty.

• Data approval:

  • In 25.05, data approval status was split from data status. Before upgrading, finalize all approvals, otherwise pre-upgrade checks may fail.

25.08

Management node security group rules

• Preserve security group rules:
  • In 25.11, firewall rules can be set via iptables on the management node. Before upgrading, install:

    # ubuntu
    sudo apt install netfilter-persistent -y
    
    # Red Hat 8
    sudo dnf install -y iptables-services iptables-utils
    sudo systemctl start iptables && sudo systemctl enable iptables
    # Restart Docker after installation
    sudo systemctl restart docker
  • If the management node already has iptables firewall rules, those rules will not be cleared, but their priority may be reduced and could be impacted.