VMware Telco Cloud Automation 2.3.0.1 Release Notes

VMware Telco Cloud Automation 2.3.0.1 | 6 Jun 2023 | Build - VM-based: 21843249

What's New

VMware Telco Cloud Automation version (TCA) 2.3.0.1 delivers critical fixes for version 2.3.

Important Notes

• 2.3 BYOI Templates for VMware Tanzu Kubernetes Grid continue to work for VMware Telco Cloud Automation 2.3.0.1.

• Upgrades from VMware Telco Cloud Automation 2.2 to VMware Telco Cloud Automation 2.3.0.1 are supported.

• Upgrades from VMware Telco Cloud Automation 2.3 to VMware Telco Cloud Automation 2.3.0.1 are supported.

• No change or upgrade is required for CaaS clusters when upgrading from TCA 2.3.0 to TCA 2.3.0.1.

• CaaS management cluster upgrades are mandatory when upgrading from TCA 2.2 to TCA 2.3.0.1.

Resolved Issues

• RBAC
• CNF LCM
• Catalog Management
• Kubectl and SSH

RBAC

• Fixed issue 3220967:

  When an RBAC user logs in, creates a Network Function catalog with 3.0 workflows, and runs the workflow, the user is redirected to a different workflow.

• Fixed issue 3220461:

  When the user does not have access to all the VIMs and few of the non-accessible VIMs are associated with the partner systems, the Partner Systems page fails to load for such users.

• Fixed issue 3220042:

  The count of the clusters displayed on the CaaS Infrastructure page is incorrect for non-system administrators who do not have access to all clusters.

• Fixed issue 3219682:

  When you log in as an RBAC user, v1 node pools are not listed in the UI and the LCM operation fails for v2 node pools.

• Fixed issue 3217814:

  The Partner Systems page fails to load when a user has access only to cloud VIMs.

• Fixed issue 3215671:

  "Any of" condition does not work as expected in advanced filters when used along with other operators such as "equal to" and "not equal to".

• Fixed issue 3215197:

  Setting multiple tag filters does not work as expected for users with workflow privileges.

• Fixed issue 3211268:

  Unable to instantiate a virtual network function for non-admin users when the advanced filter is added to the catalog.

CNF LCM

• Fixed issue 3223223:

  Termination of a CNF instance can cause corruption of the state of another CNF instance.

Catalog Management

• Fixed issue 3223224:

  When onboarding a new CSAR, the properties of an existing CSAR are updated with the newly created CSAR values.

Kubectl and SSH

• Fixed issue 3178722:

  When VMware Telco Cloud Automation is used with AD-based authentication, opening the terminal for VIMs and NFs fails.

Known Issues

• RBAC
• User Interface
• VNF LCM
• Workflows

RBAC

• Issue 3220059: If RBAC permissions are modified after creating the NF instance, accessing the underlying NF catalogs and VIMs displays an error

  After the NF instance is created, if RBAC permissions are modified to remove access for NF catalogs and VIMs, then the underlying NF catalogs and VIMs are not visible to the user and when the user tries to access them, an error is displayed.

  Workaround:

  Ensure that parent objects of user-owned objects are accessible to the user.

• Issue 3219731: RBAC advanced filter does not support filtering the Virtual Infrastructure by Public Cloud types

  RBAC advanced filter does not support filtering the Virtual Infrastructure by Public Cloud types as shown in UI. For example, RBAC advanced filter is not available for Amazon EKS, Amazon Cloud Services, Google Cloud, and so on.

  Workaround:

  Use the underlying VIM type for filtering Public Clouds. For example, use KUBERNETES for Amazon EKS.

• Issue 3220592: The new VIM created by the VIM administrator is not seen in the search result when the advanced filter is applied with the “name” condition

  As a Virtual Infrastructure Manager (VIM) administrator, if you use the advanced filters with the “name” condition to search for the VIMs, then the newly created VIM is not listed in the search result.

  Workaround:

  If there is a predefined list of VIMs in the advanced filter, add the new VIM name to the predefined list.

• Issue 3220592: The new VIM created by the VI administrator is not seen in the search result when the advanced filter is set with the “name” condition

  If a Virtual Infrastructure (VI) administrator has an advanced filter with the “name” condition to filter the VIMs, the VIM created by the VI administrator is not listed in the search result.

  Workaround:

  If there is a predefined list of VIMs in the advanced filter, then add the new VIM name to the predefined list.

• Issue 3220705: Disassociating a VIM from the harbor from a user who is not a system administrator leads to the removal of VIMs from that harbor

  If a user who is not a system administrator disassociates a VIM from the harbor, all the VIMs from that harbor are removed.

  Workaround:

  If you are not a system administrator with complete access to the VIMs, do not perform the edit operations in shared partner systems.

User Interface

• Issue 3211123: When editing the CaaS v1 template, the "Next" button is disabled in the "Control Plane Node Configuration" tab

  Workaround:

  To enable the Next button:

  1. Expand Advanced Configuration.

  2. Under Machine Health Check >> Node Unhealthy Conditions, remove the blank rows.

VNF LCM

• Issue 3220048: Additional operations are enabled if the Reset State operation is performed when the Heal operation fails on the NF instance

  Additional operations such as Operate, Upgrade Package, and Run Workflow are enabled if the Reset State operation is performed when the Heal operation fails on the NF instance.

Workflows

• Issue 3220082: Workflow catalog filters do not work

  Workflow catalog filters such as Version, Schema Version, Created By, Read Only, and Created On do not work.

• Issue 3221536: Files uploaded during the execution of standalone Workflows are corrupted

  If the file input is provided during runtime, when executing a standalone workflow, the file gets corrupted.

  Workaround:

  Execute such workflows as part of the NF / NS catalog.

  Note:

  Attach the files when designing the standalone workflow.