Error: NodePolicy validation fails with "invalid package version suffix" during NF instantiation in TCA

Products

• VMware Telco Cloud Automation

Issue/Introduction

While instantiation the network function, below error is faced:

Error message: [PolicyValidationError] Generate nodepolicies for generation 1 failed, reason:
Apply nodepolicy to mc failed, error: admission webhook "validator.vmconfig.acm.vmware.com" denied the request: 
NodePolicy.acm.vmware.com "<POLICY_NAME>" is invalid: spec.nodeconfig: Invalid value: "nodeprofile": packages merge failed: 
packages conflict: invalid package version <VERSION>.ph5, version should have suffix .ph3 or .ph2null

• NodePolicy status remains in "Failed" state.

Environment

3.2

Cause

The Management Cluster (MC) addons are running on an older TCA BOM Release (typically TCA 2.3), which only supports Photon OS 2 (.ph2) and Photon OS 3 (.ph3) package schemas. The Network Function operation includes package requirements for Photon OS 5 (.ph5), which the older vmconfig validator does not recognize, leading to a package merge conflict.

Resolution

To resolve this issue, the TCA environment and Management Cluster addons must be aligned to version 3.2 or higher to support Photon 5 package validation. 

Verify the addon version.

• Login to the management cluster and check the addon version:
  

  kubectl get pkgi -A

• Check the addon version from the Database.
  Login to the TCA-M and connect to postgress
  

  kubectl exec -it postgres-0 -n tca-mgr -- psql -d tca -U tca_admin -h localhost

• Run the below command to check the version

  select val ->> 'clusterName' as clustername, id, val ->> 'id' as caasid, val ->> 'rowType' as rowtype, val ->> 'clusterType' as clustertype, val ->> 'name' as name, val ->> 'clusterId' as clusterid, val -> 'metadata' ->> 'name' as metadataname, val -> 'metadata' ->> 'clusterName' as MetadataClusterName, val -> 'spec' -> 'tcaBomReleaseRef' ->> 'name' as tbr, val -> 'spec' -> 'controlPlaneSpec' -> 'tcaBomReleaseRef' ->> 'name' as cptbr, val -> 'status' ->> 'kubernetesVersion' as k8sversion from "K8sClusterDetails";

  If there is a mismatch of the addon version then proceed with the upgrade of management cluster addons.

Additional Information

• Reference Documentation: Upgrade Workload Kubernetes Cluster Version

• Note: Failure to upgrade MC addons after a TCA manager upgrade will result in persistent validation failures for newer OS schemas.