Execute the Upgrade Script

Execute the
upgradeTCSA.sh
script located in
tcx-deployer/scripts
.
During the upgrade process, you cannot access the
VMware Telco Cloud Service Assurance
UI.
To generate the self-signed certificates for Harbor, perform the following procedure:
  1. Copy the Harbor Certs file in the
    /etc/ssl/certs
    directory.
  2. If you do not have permission to the
    /etc/ssl/certs
    directory, then put the Harbor Cert in any other location where you have access, and run the below command:
    trust anchor <path-to-cert>
    You must set this tag to false if it is set to true
    export PUSH_TO_CHART_REPO=false
  3. If trust command is not available, then install
    p11-kit-trust
    package, which contains the trust command.
    1. If you do not want to specify the registry user name and password in the installation script, perform Docker login.
      To log in to Docker, run the following command:
      docker login <harbor-fqdn>
    2. Ensure that the registry password does not have a comma in it. If a comma is used, replace it using the backslash.
    Execute the
    upgradeTCSA.sh
    script.
    root [ ~ ]# cd $TCSA_WORK_SPACE/tcx-deployer/scripts root [ ~/upgrade/tcx-deployer/scripts ]# ./upgradeTCSA.sh --kubeconfig <your-kubeconfiglocation> --registry <harbor-registry-fqdn>/<project-name> --registry-cert <path-to-the registry-ca-certificate-file> --registry-password <harborregistry-password> --registry-username <harbor-registry-username> --timeout <timeout in minute>
    It is recommended to specify 90 minutes for the timeout value. If there is any latency in the network, then this value can be further increased.
    After the upgrade script exits, manually check the
    VMware Telco Cloud Service Assurance
    deployment status by running the following command from the deployment VM.
    root [ ~/tcx-deployer/scripts ]# kubectl get tcxproduct
    or
    root [ ~/tcx-deployer/scripts ]# kubectl get apps
    For all the applications, the reconciliation status must be successful.
    root [ ~/tcx-deployer/scripts ]# kubectl get tcxproduct NAME STATUS READY MESSAGE AGE tcsa updateCompleted True All App CRs reconciled successfully 30h
    • After a successful upgrade, you can launch the
      VMware Telco Cloud Service Assurance
      UI. For more information, see Accessing VMware Telco Cloud Service Assurance UI topic. Ensure that the About page in VMware Telco Cloud Service Assurance UI reflects the upgraded version of VMware Telco Cloud Service Assurance.
    • If the
      Isitio-edge-ingressgateway
      pod fails with
      ImagePullBackOff
      error, then refer to the Pod fails with ImagePullBackOff error section in the
      VMware Telco Cloud Service Assurance Troubleshooting Guide
      .
  4. After the upgrade is successful, you must execute the
    postUpgrade.sh
    script for cleaning the stale entries from the deployer host.
    $TCSA_WORK_SPACE/tcx-deployer/scripts/postUpgrade.sh <your-kubeconfig-location>