This site will be decommissioned on December 31st 2024. After that date content will be available at techdocs.broadcom.com.

 

VMware Telco Cloud Automation 2.1.1 | 22 SEP 2022 | Build - VM-based: 20494210, HA-based: 20494148

Check for additions and updates to these release notes.

What's New

VMware Telco Cloud Automation version (TCA) 2.1.1 delivers critical fixes for version 2.1 and includes the following new capabilities:

  • An updated set of VMware General Terms.

  • Increased limit from 500 KB to 5 MB for consolidated values.yaml for CNF instantiation and upgrades.

  • Availability of official error codes for various failure scenarios.

  • Enhancements in Infrastructure Automation for cell site provisioning.

  • Several bug fixes.

Photon BYOI templates and RAN Optimized BYOI templates for TKG 1.5.4 are also available under Drivers and Tools tab on Customer Connect. For instructions on accessing and downloading compatible BYOI templates, see the Important Notes section.

Important Notes

  • Download RAN Optimized BYOI Templates for VMware Tanzu Kubernetes Grid

    To download RAN optimized BYOI templates, perform the following steps:

    1. Go to the VMware Customer Connect site at https://customerconnect.vmware.com/.

    2. From the top menu, select Products and Accounts > All Products.

    3. In the All Downloads page, scroll down to VMware Telco Cloud Automation and click Download Product.

    4. In the Download VMware Telco Cloud Automation page, ensure that the version selected is 2.1.1.

    5. Click the Drivers & Tools tab.

    6. Expand the category VMware Telco Cloud Automation RAN Optimized BYOI Template for TKG.

    7. Corresponding to RAN Optimized Photon BYOI Templates for VMware Tanzu Kubernetes Grid 1.5.4, click Go To Downloads.

    8. In the Download Product page, download the appropriate Photon BYOI template.

  • Download Photon BYOI Templates for VMware Tanzu Kubernetes Grid

    To download Photon BYOI templates, perform the following steps:

    1. Go to the VMware Customer Connect site at https://customerconnect.vmware.com/.

    2. From the top menu, select Products and Accounts > All Products.

    3. In the All Downloads page, scroll down to VMware Telco Cloud Automation and click Download Product.

    4. In the Download VMware Telco Cloud Automation page, ensure that the version selected is 2.1.1.

    5. Click the Drivers & Tools tab.

    6. Expand the category VMware Telco Cloud Automation Photon BYOI Templates for TKG.

    7. Corresponding to Photon BYOI Templates for VMware Tanzu Kubernetes Grid 1.5.4, click Go To Downloads.

    8. In the Download Product page, download the appropriate Photon BYOI template.

Resolved Issues

The following issues are resolved for this release.

CNF LCM

  • Fixed Issue 3021254

    CNF Reinstantiation fails on a CaaS cluster that was deleted and recreated with the same information.

  • Fixed Issue 3027489

    If you run Reconfigure or Scale with invalid Harbor credentials, CNF is rolled back to version 1.

  • Fixed Issue 3010153

    Unable to perform CNF Upgrade if the corresponding VDU or helm chart names are different in the CSARs.

  • Fixed Issue 2992924

    CNF instantiations and upgrades fail if the values.yaml is larger than 500 KB.

Infrastructure Automation

  • Fixed Issue 2983990

    Cell site host provisioning fails if the host does not have a port group by name 'VM Network'.

  • Fixed Issue 2998610

    Force delete fails to clean up some hosts from vCenter Server.

  • Fixed Issue 3017442

    In a scaled environment, deletion of hosts across multiple domains fails due to timeout.

  • Fixed Issue 3018467

    UI truncates the alert text when the error message is big.

  • Fixed Issue 3018803

    No error message is seen when host deletion fails.

  • Fixed Issue 3023126

    High CPU usage seen when provisioning cell site hosts in parallel.

  • Fixed Issue 3023536

    Infrastructure Automation fails to clean up VMware Telco Cloud Automation inventory for deleted hosts.

  • Fixed Issue 3030155

    Cell site group status is not reflecting the correct status when one or more hosts are being deleted.

  • Fixed Issue 3032730

    Host setting status is marked as failed on all the hosts in the batch even if host profile failed to apply on one host or a subset of hosts.

Cluster Automation

  • Fixed Issue 3022367

    UI does not load Node Pool details correctly if the Node Pool does not have any labels.

  • Fixed Issue 3013770

    System Settings and Harbor add-ons are not listed in the UI for transformed Imported Clusters.

  • Fixed Issue 3007749

    Some of the cluster LCM operations fail post transformation to v2 in a multi vCenter scenario.

  • Fixed Issue 3005073

    On v2 clusters, the Delete Node Pool operation hangs if the v2 cluster contains a label with a dot.

  • Fixed Issue 2988552

    Fails to upgrade management cluster. One of the control plane nodes displays the status as SchedulingDisabled.

HA-Based TCA

  • Fixed Issue 3008209

    Uploading backups to the FTP server does not work.

  • Fixed Issue 3004674

    Unable to add VMware Cloud Director VIM.

Appliance UI

  • Fixed Issue 3003849

    Kernel arguments applied to the node pool during NFV instantiation are not visible on the User Interface (UI).

Node Customization

  • Fixed Issue 2984947

    vmconfig operator constantly logs events for deleted NodePolicyMachineStatus.

  • Fixed Issue 3002924

    After the Control Plane BOM upgrade, the Edit Node Pool operation lists Control Plane Kubernetes version templates instead of Node Pool Kubernetes version templates.

  • Fixed Issue 3005235

    In the CSAR Designer, Add Network Adapter with device type vmxnet3 does not show the Resource Name.

Partner System

  • Fixed Issue 3001322

    Adding custom port Harbor to the v2 clusters causes Harbor add-on to freeze.

Backup and Restore

  • Fixed Issues 3000826, 3001365, and 3017472

    After the backup and restore of operations from one VMware Telco Cloud Automation appliance to another, some of the functions on the CaaS clusters fail.

Known Issues

HA-Based TCA

  • Issue 3033933: TCA upgradation fails after restoring the backup bundle

    After restoring a backup bundle, the upgrade of HA-based TCA to a later build fails.

Cluster Automation

  • Issue 3036626: Customizations on the Node Pool fail when the Node Pool is in maintenance mode

    When a Node Pool is in maintenance mode, any further customizations on the Node Pool might fail.

    Workaround:

    Exit maintenance mode on the Node Pool. After you exit, the previous customizations are triggered on the Node Pool.

Helm Service

  • Issue 3031896: Helm service fails to start on the TCA-CP appliance

    Helm service fails to start on the TCA-CP appliance when there are orphan CNF entries in the TCA-CP database.

    Workaround:

    Run the Sessions API on TCA-CP.

    curl --location --request POST 'https://<tca-cp>/hybridity/api/sessions' \ --header 'Accept: application/json' \ --header 'Content-Type: application/json' --data-raw '{ "username":"<username-for-vcenter-for-tca-cp>", "password":"<password>" }'

    Disable the Extension Platform Service.

    curl --location --request PUT 'https://<tca-cp>/admin/hybridity/api/global/settings/ExtensionPlatform/disableRepoExtensionGroup' \ --header 'x-hm-authorization: <copy-from-sessions-API-response-headers>' \ --header 'Accept: application/json' \ --header 'Content-Type: application/json' \ --data-raw '{ "value": "true" }'

    Ensure that the helm service is running automatically. If not, start the helm service as a root user on TCA-CP.

    systemctl start helm-service

Node Customization

  • Issue 3037896: "Upgrade VM Hardware Version" is not applied on newly created node pools of v2 CaaS Workload clusters

    The node customization option to upgrade VM hardware version to the latest is not applied on newly created node pools of v2 CaaS Workload clusters.

    Workaround:

    To upgrade the VM hardware version, create the node pools in one of the following ways:

    1. On Workload clusters that are transformed from v1 to v2, use the Deploy Similar Node Pool option from the existing node pool.

    2. On v2 Workload clusters that are created in VMware Telco Cloud Automation 2.1.1, ensure that you provide all the details when adding the node pool from the user interface. Before deploying the v2 Workload cluster, switch to the Custom Resources (CR) tab and edit the datastore value from full path to only name.

    3. If you have created the node pool using APIs, pass only the name of the datastore instead of the full path in the Request Payload field.

Kubectl and SSH

  • Issue 3096058: Open Terminal fails if TCA-M logged-in user has a different domain

    Open Terminal fails if TCA-M logged-in user has a domain different from the one configured within TCA-M Appliance Management.

    Workaround:

    Use the same domain name for the primary user configured within TCA-M Appliance Management.

    Note:

    The primary user must have vCenter admin access to read users and groups.

check-circle-line exclamation-circle-line close-line
Scroll to top icon