EDGE_CLUSTER_EXAPNSION_COMPLIANCE_FAILURE - Edge cluster compliance check failures (Edge nodes must be in a resource pool, but these are not []).

Products

• VMware SDDC Manager

Issue/Introduction

• NSX-T edge node expansion validation through API fails.
  
  
• The error cause is EDGE_CLUSTER_EXAPNSION_COMPLIANCE_FAILURE - Edge cluster compliance check failures (Edge nodes must be in a resource pool, but these are not [edge_node01,edge_node02]).
  
  
• Validating the edge node VMs from the vCenter server indicates the edge VMs are not part of the resource pool. 
  or
• The resource pool has been renamed from the vCenter server.
  
  
  

Environment

VMware Cloud Foundation 4.x
VMware Cloud Foundation 5.x

Cause

The resource pool was accidently deleted while disabling DRS. When disabling DRS, the resource pools are removed from the cluster - Retaining resource pools when disabling VMware DRS clusters in the vSphere Web Client

Resolution

Edge node deployment and redeployment will fail due to a known issue, apply the workaround in the following KB before proceeding, "OVF certificate validation failed. Error: [VALIDATION_ERROR: CERTIFICATE_EXPIRED; ]" error for NSX Edge Install/Redeploy/Resize.


Use the NSX-T Edge Node Virtual Machine Resizing Tool.

• Even if the Edge node VMs have been re-added to a resource pool on the vCenter, VCF will be unaware of the change. 
  
  
• VCF relies on the NSX-reported "compute_id" property to find the current resource pool for each Edge node. However, once an Edge node VM is removed from a resource pool, even if it is re-added to a resource pool NSX will continue to report the node's "compute_id" as the whole VC cluster, not just the resource pool.
  
  
• The NSX-T edge node resize tool for VCF, is used for resizing Edge nodes. This also corrects the resource pool association reported by NSX so that it properly reflects the Edge node's current resource pool placement (if any). 
  
  Resolution Steps involves us to resize the edge nodes to its existing form factor.  

1. 1. Download the edge_cluster_node_resize script from the NSX-T Edge Node Virtual Machine Resizing Tool KB.

   2. Run the --list-sizes option to show what form-factor is presently assigned to each Edge node (it should be the same for all Edge nodes in an Edge cluster, if no out-of-band changes have been made)
      
      ./resize.sh --edge-cluster <cluster_name> --user <ssoUser> --password '<ssoUserPassword>' --list-sizes

   3. Run  --form-factor {SMALL,MEDIUM,LARGE,XLARGE} --force, which makes the Edge node deployment happen even if the form-factor remains the same. You must specify the existing form factor as you want to keep the same size.
      
      ./resize.sh --edge-cluster <cluster_name> --user <ssoUser> --password '<ssoUserPassword>' --form-factor {SMALL,MEDIUM,LARGE,XLARGE} --force
      
      
   4. Once the script has run successfully, re-run the validations for the Edge node expansion from the SDDC API.
      
      Note: The downside to this script is that the resize requires a redeploy of each Edge node.
      It does the Edge nodes one at a time, but for a two-node Edge cluster, this may temporarily cut the cluster's compute and network throughput by 50%, however the process is quick without a noticeable downtime. Once the resize has completed, the cluster should work just as it did before. 
      Before recommending a larger form factor or expanding an edge cluster, we must verify the customer's available core licensing. This ensures that the increased core consumption does not result in unexpected overage charges