Performing a software upgrade
You 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 10.254.106.74 Time difference is 0 seconds Timesync service is running on 10.254.106.75 Time difference is 0 seconds Timesync service is running on 10.254.106.76 Time difference is 0 seconds Timesync service is running on 10.254.106.77 Time difference is 0 seconds Timesync service is running on 10.254.106.78 Time difference is 0 seconds Timesync service is running on 10.254.106.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 discoverTrying to discover fss-node01 10.254.106.74 Trying to discover fss-node02 10.254.106.75 Trying to discover fss-node03 10.254.106.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_4_B1-charts-v23.4.1-119 -
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_4_B1-charts-v23.4.1-119 to fss-FSS_23_8_B1-charts v23.8.2-yyy : Are you sure [YyNn]? y Upgrade in progress... Upgrading fss-logs Upgrading traefik and ingress routes traefik release discovered: traefik-10.14.2 ; Deployer packages traefik release: traefik 21.0.0 Upgrading kafka and kafkaop if required KAFKA not present. Installing fresh Error from server (NotFound): secrets "kafka-fss-cluster-ca-cert" not found Error from server (NotFound): secrets "kafka-fss-clients-ca-cert" not found W0529 07:14:29.567723 7676 warnings.go:70] policy/v1beta1 PodDisruptionBudget is deprecated in v1.21+, unavailable in v1.25+; use policy/v1 PodDisruptionBudget W0529 07:14:29.575490 7676 warnings.go:70] policy/v1beta1 PodDisruptionBudget is deprecated in v1.21+, unavailable in v1.25+; use policy/v1 PodDisruptionBudget Release "prod" has been upgraded. Happy Helming! NAME: prod LAST DEPLOYED: Mon May 29 07:14:18 2023 NAMESPACE: default STATUS: deployed REVISION: 2 NOTES: Checking for FSS pods Waiting for default fss-auth 1 Running Waiting for FSS pods to comeup Waiting for default fss-auth 1 Running Waiting for FSS pods to comeup Waiting for default fss-cfgsync 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 ready, you can access FSS using https://prod.k8s.nokia.com -
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.