Performing a software upgrade
Use the fss-upgrade.sh script to perform the software upgrade
steps. The command syntax is as
follows:
[root@fss-deployer ~]# /root/bin/fss-upgrade.sh
Usage: /root/bin/fss-upgrade.sh configure <config-file> - Reads config file and configures accordingly.
./bin/fss-upgrade.sh discover - Discovers cluster.
./bin/fss-upgrade.sh upgrade - Upgrades FSS application.
./bin/fss-upgrade.sh status - Prints status of cluster and FSS Chart information.
./bin/fss-upgrade.sh clean - Cleans temporary files.
./bin/fss-upgrade.sh [help | -h] - Prints usage.This script updates the entire Fabric Services System application using the new Helm charts.
Using the new deployer VM, upgrade the Fabric Services System application in place on the existing Fabric Services System cluster.-
Update the configuration.
In the following example, the input configuration file is customer-input.json.
[root@fss-deployer ~]# /root/bin/fss-upgrade.sh configure customer-input.json Timesync service is running on 192.0.2.74 Time difference is 0 seconds Timesync service is running on 192.0.2.75 Time difference is 0 seconds Timesync service is running on 192.0.2.76 Time difference is 0 seconds Timesync service is running on 192.0.2.77 Time difference is 0 seconds Timesync service is running on 192.0.2.78 Time difference is 0 seconds Timesync service is running on 192.0.2.79 Time difference is 0 seconds Maximum time difference between nodes 0 seconds Successfully configured. Please run /root/bin/fss-upgrade.sh discover -
Discover the cluster.
[root@fss-deployer ~]# /root/bin/fss-upgrade.sh discover Trying to discover fss-node01 192.0.2.74 Trying to discover fss-node02 192.0.2.75 Trying to discover fss-node03 192.0.2.76 NAME STATUS ROLES AGE VERSION fss-node01 Ready control-plane,master 14h v1.23.1 fss-node02 Ready control-plane,master 14h v1.23.1 fss-node03 Ready control-plane,master 14h v1.23.1 fss-node04 Ready <none> 14h v1.23.1 fss-node05 Ready <none> 14h v1.23.1 fss-node06 Ready <none> 14h v1.23.1 FSS release discovered fss-FSS_23_8_B1-charts-v23.8.4-35 -
Upgrade the Fabric Services System application.
[root@fss-deployer ~]# /root/bin/fss-upgrade.sh upgrade NAME STATUS ROLES AGE VERSION fss-node01 Ready control-plane,master 75m v1.23.1 fss-node02 Ready control-plane,master 74m v1.23.1 fss-node03 Ready control-plane,master 74m v1.23.1 fss-node04 Ready <none> 73m v1.23.1 fss-node05 Ready <none> 73m v1.23.1 fss-node06 Ready <none> 73m v1.23.1 FSS will be upgraded from fss-FSS_23_8_B1-charts-v23.8.4-12 to fss-FSS_24_5_B1-charts-v24.5.1-269 : Are you sure [YyNn]? y Upgrade in progress... Upgrading fss-logs fss-logs release discovered: fluent-bit-0.20.9 ; Deployer packages fss-logs release: fluent-bit 0.39.0 Upgrading cert-manager cert-manager release discovered: cert-manager-v1.12.0 ; Deployer packages cert-manager release: cert-manager v1.13.3 cert-manager upgrade started Upgrading metallb metallb release discovered: metallb-0.13.7 ; Deployer packages metallb release: metallb 0.13.7 metallb upgrade not required Upgrading traefik and ingress routes traefik release discovered: traefik-21.0.0 ; Deployer packages traefik release: traefik 26.0.0 Upgrading kafka and kafkaop if required kafkaop release discovered: strimzi-kafka-operator-0.31.0 ; Deployer packages kafkaop release: strimzi-kafka-operator 0.37.0 NEW KAFKA operator, upgrade chart and update kafka Waiting for fss services to stop KAFKA will be deleted and reinstalled. Upgrading / Installing new FSS Chart Release "prod" has been upgraded. Happy Helming! NAME: prod LAST DEPLOYED: Mon Mar 18 06:42:09 2024 NAMESPACE: default STATUS: deployed REVISION: 3 NOTES: KAFKA being reinstalled. Checking for FSS pods Waiting for default fss-catalog 1 Running Waiting for FSS pods to comeup Waiting for default fss-version 1 Running Waiting for FSS pods to comeup All FSS pods are running Checking for FSS digitalsandbox pods FSS digital sandbox pods are running Checking for digitalsandbox pods Digital sandbox pods are running FSS is started, it can take upto 10 mins to be ready for use GUI can be accessed at https://192.0.2.74 -
Verify that the upgrade is successful.
-
Restore previously added software catalog images.
The upgrade procedure replaces the software catalog. Changes that you made to the software catalog are lost after the upgrade. If you previously added new SR Linux images to the software catalog, you need to modify the software catalog and then upload the SR Linux images. For instructions, see
Adding a network operating system version to the software catalog
in the Fabric Services System User Guide. You must complete this step before you can access the Fabric Services System to make any change.