Upgrading solution services

Last Updated : Dec 20, 2022 |
Prolog information
The cluster upgrade takes a minimum of one hour. During the upgrade, folders and virtual machines are created on the host machines visible in the vCenter of the host.
Before you begin
Restart the CCM local Docker registry and ChartMuseum processes.
  1. Log in to the Cluster Control Manager (CCM) console as the customer user.
  2. Use a utility, such as WinSCP, to transfer the solution configuration spreadsheet to the ~/artifacts directory.
    ADDITIONAL INFORMATION:
    Note:
    This spreadsheet is the file you used to download the Avaya Analytics™ software artifacts to the PC or laptop.
  3. 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.
  4. Run the ccm upgrade spec <solution spreadsheet name>.xlsm --products --force command.
  5. At the prompt, enter your vCenter credentials.
  6. At the prompt, enter your Avaya SSO credentials.
    ADDITIONAL INFORMATION:
    Note:
    You must enter your CCM local registry username and password that you earlier configured with the agn-ctl-setup command.
  7. At the prompt, confirm the cluster upgrade to the new version specified in the solution spreadsheet.
  8. 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.
  9. To take a backup, enter y.
    ADDITIONAL INFORMATION:
    • Entering n cancels the operation.
    • Entering y runs a backup after the upgrade is complete.
    STEP RESULT:
    The backup takes approximately 5 to 10 minutes to complete. The backup file is located at /var/avaya/artifactCache/
  10. To restore the operation, enter the password when prompted.
  11. To monitor the progress of the upgrade, run the following command:
    ADDITIONAL INFORMATION:
    tail -f /var/log/avaya/ccm/ccm-main.log
  12. If the upgrade exits with an error, run the following command again: ccm upgrade spec <solution spreadsheet name>.xlsm --products --force
  13. Stop the local CCM Docker registry and ChartMuseum. See section Stopping ChartMuseum and Docker registry on ClusterControl Manager in this section.
  14. Log in to the Cluster Control Manager (CCM) console as the customer user.
  15. Switch to being the root user by entering the command su.
  16. After the upgrade is completed, restart the 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