Upgrading solution services

Last Updated : Dec 20, 2022 |
Prolog information
Upgrade the services in the solution(s).
Before you begin
Ensure that the Cluster Control Manager and cluster nodes are upgraded before proceeding with the services upgrade.
Do not continue with the solution service upgrade unless all services, except for tools-policy and utility-service, are DEPLOYED and show RUNNING or COMPLETE.
  1. Log in to Cluster Control Manager with your customer account.
  2. To run the upgrade in the background, at the CCM prompt, type screen.
    ADDITIONAL INFORMATION:
    When running the upgrade in the background, if you need to detach from the upgrade SSH session, see Detaching from the upgrade SSH session.
  3. Run the ccm upgrade spec <complete path>/<solution spreadsheet name>.xlsx --products command.
  4. When prompted, type y to confirm the requested products to upgrade to the new versions specified in the solution spreadsheet and to accept the warning reminding you to start a screen session.
    ADDITIONAL INFORMATION:
    Only type y if you have already run screen. Do not continue with the upgrade until you do this.
    Failure to run the screen command exits the process and you have to start over.
  5. When prompted, accept the EULA.
    ADDITIONAL INFORMATION:
    Validation runs after accepting the EULA. If any part of the validation fails, you must address the detected issues and restart the upgrade.
  6. When prompted to perform a backup, enter y or n.
    ADDITIONAL INFORMATION:
    If you enter y, a backup runs after the upgrade is complete. The backup takes approximately 5 to 10 minutes to complete. If the archive destination is set to Local, the backup file is located at /var/avaya/artifactCache/ccmClusterBackup. If the archive destination is set to Remote, the ccmClusterBackup folder, which contains the backup file, is located in the base directory you specified.
  7. To monitor the progress of the upgrade, run the tail -f /var/log/avaya/ccm/ccm-main.log command.
  8. If the upgrade exits with an error, run the ccm upgrade spec <solution spreadsheet name>.xlsm --products --force command again.
  9. Wait approximately 30 minutes, then run ccm smoke-test on Cluster Control Manager and confirm that all tests pass. If ccm smoke-test fails, run it again in 10 minutes. If the test continuously fails for over an hour, contact your technical support representative.
  10. Log in to the Cluster Control Manager (CCM) console as the customer user.
  11. Switch to being the root user by entering the command su.
  12. After the upgrade is completed, restart database pods by running the following command and wait till the database pods are in running state:
    ADDITIONAL INFORMATION: kubectl get pod --no-headers -o custom-columns=":metadata.name" | grep analyticsdb-node- | xargs kubectl delete pod