Below steps document the procedure to follow for upgrading your Concerto cluster, we have used 11.4.2 release as an example

Step 1: Download the 11.4.2 bin file to /var/versa/ecp/share/packages directory on the primary node (or any one of the nodes in the cluster) and set up the file permissions. The bin file is synced to all other nodes in the cluster.

For example (note that the image name can vary depending on the hot-fix you may be using)

        1) sudo cp  concerto-20240117-233049-8cdfdea-11.4.2.bin /var/versa/ecp/share/packages

         2) cd /var/versa/ecp/share/packages

         3) sudo chmod 775 concerto-20240117-233049-8cdfdea-11.4.2.bin   

         4) sudo chown versa:versa concerto-20240117-233049-8cdfdea-11.4.2.bin

Step 2: Wait for a few minutes and check on all the nodes to verify if .bin package is present under /var/versa/ecp/share/packages and permissions are reflected

Step 3: Make sure concerto is running and all database replicas are in sync  ("vsh status" & "vsh database status")

Step 4: Perform the full back-up of the Concerto using "vsh database backup create" and validate if the new backup is available by checking "vsh database backup list"

Step 5: Perform upgrade on the Primary node of the concerto (for example, "vsh system package upgrade concerto-20240117-233049-8cdfdea-11.4.2.bin"). Note that you just need to execute this soley on the "primary" node, this will trigger the upgrade process on all the nodes in the cluster.

Step 6: The upgrade debug logs are saved to the upgrade.log and install.log files in the /var/log/ecp directory.

Step 7: When the logs indicate that the upgrade has completed, check "vsh status" to validate the status of services and check if the new package info is reflected in "vsh system details"

Step 8: Login to the primary node and validate the cluster status ("vsh database status" and "vsh cluster info")

Note: If the upgrade fails, the system will automatically rollback to the previous software image on all the nodes