Waiting for VPCNetworkConfiguration to be in Ready State while deploying VKS Cluster
search cancel

Waiting for VPCNetworkConfiguration to be in Ready State while deploying VKS Cluster

book

Article ID: 410911

calendar_today

Updated On:

Products

VMware vSphere Kubernetes Service

Issue/Introduction

  • Supervisor deployment is stalled at "Configured Core Supervisor Services"

  • LoadBalancer Service creation fails and the associated error can be found in NCP pod logs on the Supervisor control plane node: 

ESC[34mINFOESC[0m       ESC[33mvpc/vpc.go:766ESC[0m     VPC does not exist on NSX, creating VPC {"VPC": "vmware-system-supervisor-services-vpc"
}
ESC[34mINFOESC[0m       ESC[33mvpc/vpc.go:837ESC[0m     Creating NSX VPC        {"VPC": "vmware-system-supervisor-services-vpc_4372b78e-5a31-####-####-9171faceefa6"}
ESC[31mERRORESC[0m     ESC[33mrealizestate/realize_state.go:59ESC[0m   Found realized state with error {"result": {"Links":null,"Schema":null,"Self":null,"Revision":3,"CreateTime":17578###88043,"CreateUser":"system","LastModifiedTime":1757####134,"LastModifiedUser":"system","Protection":"NOT_PROTECTED","SystemOwned":false,"Description":null,"DisplayName":"vmware-system-supervisor-services-vpc_4372b78e-5a31-####-####-9171faceefa6","Id":"vmware-system-supervisor-services-vpc_4372b78e-5a31-####-####-9171faceefa6","ResourceType":"GenericPolicyRealizedResource","Tags":null,"OriginSiteId":null,"OwnerId":"924884fb-f248-49d4-####-0229976e4a14","ParentPath":"/default/realized-state/enforcement-points/default","Path":"/orgs/default/projects/example/realized-state/example/default/vpcs/vmware-system-supervisor-services-vpc_4372b78e-5a31-####-####-9171faceefa6","RealizationId":"a8fac4aa-048d-####-a6d9-08f0bba5540c","RelativePath":"vmware-system-supervisor-services-vpc_4372b78e-5a31-####-####-9171faceefa6","RemotePath":"","UniqueId":"a8fac4aa-048d-####-a6d9-08f0bba5540c","Alarms":[{"Links":null,"Schema":null,"Self":null,"Revision":0,"CreateTime":1757###8129,"CreateUser":"system","LastModifiedTime":1757###8129,"LastModifiedUser":"system","Protection":"NOT_PROTECTED","SystemOwned":false,"Description":null,"DisplayName":"8c639bdd-0f45-####-8258-3193183f91a8","Id":"PROVIDER_INVOCATION_FAILURE","ResourceType":"PolicyAlarmResource","Tags":null,"OriginSiteId":null,"OwnerId":"924884fb-f248-49d4-####-0229976e4a14","ParentPath":null,"Path":null,"RealizationId":"ccfcdba7-f485-####-9a83-05138c0f926e","RelativePath":"8c639bdd-0f45-####-8258-3193183f91a8","RemotePath":"","UniqueId":"ccfcdba7-f485-####-9a83-05138c0f926e","ErrorDetails":{"Details":null,"ErrorCode":10000,"ErrorData":{},"ErrorMessage":"Found errors in the request. Please refer to the related errors for details.","ModuleName":"ROUTING","RelatedErrors":[{"Details":null,"ErrorCode":10087,"ErrorData":{},"ErrorMessage":"[Routing] Insufficient resources to do auto allocation in edge cluster 51739037-d2b4-####-a998-7aabbe56a98b of pool type LB_ALLOCATION_POOL because of below reason(s).","ModuleName":"ROUTING"},{"Details":null,"ErrorCode":10149,"ErrorData":{},"ErrorMessage":"[Routing] Node(s) [EdgeTransportNode/dc011de2-c6fa-4865-####-c430a093f851] don't have enough capacity to allocate.","ModuleName":"ROUTING"}]},"Message":"Found errors in the request. Please refer to the related errors for details.","SourceReference":"/orgs/default/projects/example/realized-state/example/default/vpcs/vmware-system-supervisor-services-vpc_4372b78e-5a31-####-####-9171faceefa6","SourceSiteId":null}],"IntentReference":["/orgs/default/projects/default/example/vmware-system-supervisor-services-vpc_4372b78e-5a31-####-94cd 9171faceefa6"],"OperationalStatus":null,"OperationalStatusError":null,"PublishStatus":"UNINITIALIZED","PublishStatusError":null,"PublishStatusErrorCode":null,"PublishStatusErrorDetails":null,"PublishTime":null,"RealizationApi":null,"RealizationSpecificIdentifier":null,"RuntimeError":null,"RuntimeStatus":"UNINITIALIZED","State":"ERROR","TimeTakenForRealization":null,"EnforcementPointPath":null,"EntityType":"RealizedLogicalRouter","ExtendedAttributes":null,"IntentPaths":["/orgs/default/projects/default/example/vmware-system-supervisor-services-vpc_4372b78e-5a31-####-####-9171faceefa6"],"SitePath":null}}



Cause

Insufficient NSX Edge Node capacity: The SMALL form factor used for deployment doesn't meet the minimum capacity requirements for Cluster Supervisor Deployment with NSX as per Requirements for Cluster Supervisor Deployment with NSX

Resolution

The NSX Edge Nodes must be resized or redeployed to utilize a minimum Large form factor. Refer KB: Resize NSX Edge Node