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 ~]# ./bin/fss-upgrade.sh
Usage: ./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.
-
Update the configuration.
In the following example, the input configuration file is customer-input.json.
[root@fss-deployer ~]# ./bin/fss-upgrade.sh configure customer-input.json Timesync service is running on 192.168.59.195 Time difference is 0 seconds Timesync service is running on 192.168.59.129 Time difference is 0 seconds Timesync service is running on 192.168.59.127 Time difference is 0 seconds Maximum time difference between nodes 0 seconds Successfully configured. Please run /root/bin/fss-upgrade.sh upgrade
Note: Do not execute the fss-upgrade.sh upgrade command as indicated in the output. Continue with Step 2. -
Discover the cluster.
[root@fss-deployer ~]# ./bin/fss-upgrade.sh discover Trying to discover 192.168.59.195 Trying to discover 192.168.59.129 Trying to discover 192.168.59.127 NAME STATUS ROLES AGE VERSION fss-compute-customer-01 Ready control-plane,master 12h v1.23.1 fss-compute-customer-02 Ready control-plane,master 12h v1.23.1 fss-compute-customer-03 Ready control-plane,master 12h v1.23.1 FSS release discovered fss-FSS_22_8_B1-charts-v22.8.1-108
-
Upgrade the Fabric Services System application.
[root@fss-deployer ~]# /root/bin/fss-upgrade.sh upgrade NAME STATUS ROLES AGE VERSION fss-compute-customer-01 Ready control-plane,master 12h v1.23.1 fss-compute-customer-02 Ready control-plane,master 12h v1.23.1 fss-compute-customer-03 Ready control-plane,master 12h v1.23.1 FSS will be upgraded from fss-FSS_22_8_B1-charts-v22.8.1-108 to fss-FSS_22_8_B1-charts v22.8.2-6 : Are you sure [YyNn]? y Upgrade in progress... W1027 18:06:09.880444 7001 warnings.go:67] policy/v1beta1 PodDisruptionBudget is deprecated in v1.21+, unavailable in v1.25+; use policy/v1 PodDisruptionBudget W1027 18:06:09.888237 7001 warnings.go:67] policy/v1beta1 PodDisruptionBudget is deprecated in v1.21+, unavailable in v1.25+; use policy/v1 PodDisruptionBudget W1027 18:06:09.905507 7001 warnings.go:67] policy/v1beta1 PodDisruptionBudget is deprecated in v1.21+, unavailable in v1.25+; use policy/v1 PodDisruptionBudget W1027 18:06:09.910756 7001 warnings.go:67] policy/v1beta1 PodDisruptionBudget is deprecated in v1.21+, unavailable in v1.25+; use policy/v1 PodDisruptionBudget W1027 18:06:09.918327 7001 warnings.go:67] policy/v1beta1 PodDisruptionBudget is deprecated in v1.21+, unavailable in v1.25+; use policy/v1 PodDisruptionBudget W1027 18:06:09.927503 7001 warnings.go:67] policy/v1beta1 PodDisruptionBudget is deprecated in v1.21+, unavailable in v1.25+; use policy/v1 PodDisruptionBudget W1027 18:06:09.932171 7001 warnings.go:67] policy/v1beta1 PodDisruptionBudget is deprecated in v1.21+, unavailable in v1.25+; use policy/v1 PodDisruptionBudget W1027 18:06:09.938165 7001 warnings.go:67] policy/v1beta1 PodDisruptionBudget is deprecated in v1.21+, unavailable in v1.25+; use policy/v1 PodDisruptionBudget W1027 18:06:09.945057 7001 warnings.go:67] 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: Thu Oct 27 18:06:07 2022 NAMESPACE: default STATUS: deployed REVISION: 2 NOTES: [root@fss-deployer ~]#
-
Verify that the upgrade is successful.
-
The upgrade procedure replaces the software catalog. Changes that you made to
the software catalog will be lost. If you have added new SRL images in the
software catalog, you need to modify the software catalog and then upload the
SRL images.
For instructions, see Updating software catalog to include new versions in the Fabric Services System User Guide. You need to complete this step before you access the Fabric Services System for any changes.