Patch Tool for TCA 3.2.0.1
search cancel

Patch Tool for TCA 3.2.0.1

book

Article ID: 403159

calendar_today

Updated On:

Products

VMware Telco Cloud Automation VMware Telco Cloud Platform

Issue/Introduction

  • How to apply patch tool to TCA / airgap appliance. 
  • This TCP patch tool addresses all the issues/KBs listed below.

Issues/KBs resolved by this script

Description

ERROR: Node-Policy stage failed. Reason: nodepolicy spec is updated, waiting for reconcile.

Extend nodeconfig cert to May 8 2030.

vmconfig-operator down, in error state, when deploying multiple node pools

Fix vmconfig-operator crash when VC returns vmobj as nil;
Fix some nic renaming didn't take effect.

TBR Upgrade causes the node to rebootTBR Upgrade causes the node to reboot

Fix some nodes were reboot after upgrade to TCA3.2;
Add new feature syslog-ng forward journal log

CaaS Cluster Node Pool Creation /customization Stuck in processing state

Fix recreate cluster and nodepools with same name, old version of nodepolicy take effect.

Cluster creation stuck in provisioning status

When deploying a cluster or nodepool with a name that was used before in the environment at some point, you will see the cluster is provisioning state

KB-Monitor

Add feature to monitor cert expiration on each components

How to manually synchronize renewed CaaS kubeconfig for VMware Telco Cloud Automation 2.3

Update management cluster's kubeconfig in caas_poke database on TCA-CP

Error: "failed with newly created client is not active" during Node Pool creation/customization

Synchronize the updated kubeconfig

 

Environment

TCA 3.2.0.1

TCP 5.0

Resolution

Prerequisites

Procedure

  1. Download the patch bundle file:

  2. Copy the patch bundle file 3201-kb-bundle_v2.zip to ALL Airgap servers that are consumed by the TCA clusters.

  3. Switch to root user and unzip the patch bundle file 3201-kb-bundle_v2.zip to workload directory:

    1. #su -

    2. #unzip 3201-kb-bundle_v2.zip -d 3201-kb

    3. #cd 3201-kb

  4. Upload all KBs supported by the script:

    • #bash caas_support.sh patch upload -a <airgap-server-fqdn>

  5. Copy the patch bundle file 3201-kb-bundle_v2.zip to TCA-M.

  6. Switch to root user and unzip the patch bundle file 3201-kb-bundle_v2.zip to workload directory:

    1. SSH to TCA-M

    2. #su -

    3. #unzip 3201-kb-bundle_v2.zip -d 3201-kb

    4. #cd 3201-kb

  7. List all KBs supported by the script:

    • #bash caas_support.sh patch list

  8. Check KB status on TCA-M:

    • #bash caas_support.sh patch check

      It could return following status:

      KB status

      Comments

      NotNeeded

      KB is not needed on the current cluster.

      NotApplied

      KB is needed and not applied.

      Applied

      KB was applied successfully. When you execute apply, it will report as Skipped

      Unknown

      Can not tell the status

  9. Apply KBs on TCA-M:

    • #bash caas_support.sh patch apply

      It could return following status:

      KB status

      Comments

      NotNeeded

      KB is not needed on the current cluster.

      Skipped

      KB is already applied, skip it here.

      Succeed

      KB is applied successfully. When you execute apply again, it will report as Skipped

      Failed

      KB application failed.

  10. Copy the patch bundle file 3201-kb-bundle_v2.zip to each TCA-CP.

  11. Switch to root user and unzip the patch bundle file 3201-kb-bundle_v2.zip to workload directory:

    1. SSH to TCA-CP

    2. #su -

    3. #unzip 3201-kb-bundle_v2.zip -d 3201-kb

    4. #cd 3201-kb

  12. List all KBs supported by the script:

    • #bash caas_support.sh patch list

  13. List all clusters managed by current TCA-CP and all workload clusters managed by each management cluster:

    • #bash caas_support.sh show clusters

  14. Check KB status on each clusters:

    • #bash caas_support.sh patch check

      It could return following status:

      KB status

      Comments

      NotNeeded

      KB is not needed on the current cluster.

      NotApplied

      KB is needed and not applied.

      Applied

      KB was applied successfully. When you execute apply, it will report as Skipped

      Unknown

      Can not tell the status

  15. Apply KB status on each clusters:

    • #bash caas_support.sh patch apply

      Note: The script is reenterable, if a KB is already applied, it will return as “Skipped”

      It could return following status:

      KB status

      Comments

      NotNeeded

      KB is not needed on current cluster.

      Skipped

      KB is already applied, skip it here.

      Succeed

      KB is applied successfully. When you execute apply again, it will report as Skipped

      Failed

      KB application failed.

      Note: It is normal for the script to prompt the user to enter the TCA-M FQDN, username, and password in the command line when the fix for KB 371488 is applied.

  16. Verify KB status:

    • #bash caas_support.sh patch check

      Note      : Will return “NotNeeded” or “Applied”.

Additional Information

How to proceed if one cluster apply failed?

Most cases rerun should fix the issue. The script support apply patches to a specific cluster.

  • If the target cluster is a management cluster, use this command line

    #bash caas_support.sh patch apply -m <management-cluster-name>

  • If the target cluster is a workload cluster, mc name is required,  use the following:
    1. Query management cluster name for a workload cluster

      #bash caas_support.sh show clusters

    2. Apply patches for a workload cluster

      #bash caas_support.sh patch apply -m <mangaement-cluster-name> -w <workload-cluster-name>

      For nodeconfig, vmconfig, and monitor operator, all three components are installed/patched using PKGI. Check the `*.output` file for complete PKGI information. If rerunning does not resolve the issue, share the `*.output` file and the output of `bash caas_support.sh version` for further assistance.

Will the patch be persisted post upgrade?

  • Immediate Effect After One-Shot Patch:

    • For TCA-M/TCA-CP itself, the patch is applied and the new image takes effect immediately.

    • Upon upgrading TCA-M/TCA-CP to version 3.3.x or higher, the new image included in 3.3.x (which is presumed to contain all KB fixes) will automatically take effect without any additional steps.

  • Effect on Management and Workload Clusters:

    • If TCA is at version 3.2.0.1, the patch will automatically take effect during any subsequent cluster upgrade. No extra action is required.

    • Once TCA is upgraded to 3.3.x and the management and workload clusters are also upgraded, the new image from TCA 3.3.x (presumed to include all KB fixes) will automatically take effect. No further action is needed.

What does “caas_support.sh patch check” do?

  • The process involves iterating through all management clusters, and for each, examining its workload clusters. Subsequently, it checks all known KBs, performing the following steps for each:

    1. Verifying KB compatibility for CaaS clusters.

    2. Executing the KB's sub-script with the “--check” flag.

    3. Store each KB's sub-script  output to *.output

What does patch apply do?

  • The process involves iterating through all management clusters, and for each, examining its workload clusters. Subsequently, it checks all known KBs, performing the following steps for each:

    1. Verifying KB compatibility for CaaS clusters.

    2. Executing the KB's sub-script with the “--apply” flag.

    3. Store each KB's sub-script  output to *.output

Powered by Wolken Software