Reconciling VCF services runtime nodes resource pool placement after manual migration of nodes in vCenter
search cancel

Reconciling VCF services runtime nodes resource pool placement after manual migration of nodes in vCenter

book

Article ID: 455864

calendar_today

Updated On:

Products

VCF Operations

Issue/Introduction

After manually migrating VCF services runtime nodes (e.g., during cluster consolidation) to a different resource pool, infrastructure details show stale entries when navigating to Build → Lifecycle → VCF Management → VCF Services Runtime component in VCF Operations.

Environment

VCF Operations 9.1.x

Cause

In VMware Cloud Foundation 9.1.x, VCF services runtime nodes must not be manually relocated to different resource pools after deployment. Once moved manually, even if re-added to a resource pool, the VCF internal references often remain inconsistent with the vCenter configuration. It is required to perform the runtime placement when these nodes have already been manually migrated.

Resolution

To perform a manual reconsolidation, follow the steps mentioned below:
  1. Log in to the VMSP control plane node as vmware-system-user and switch to the root user: 
    sudo su -
  2. Check the existing configuration to review the current resource pool details by running the following command: 
    kubectl get pd -n vmsp-platform vmsp-platform -o yaml | grep vsphere
  3. Update the pd configuration to align the cluster, clusterId, resourcePool, and resourcePoolId with the current vSphere environment using: 
    kubectl edit pd -n vmsp-platform vmsp-platform

  4. Save the configuration and the pd service gets restarted automatically when the yaml file is saved.
  5. New machines will start getting provisioned with the correct configuration. Machine creation status can be checked by running the following command: 
    kubectl get machine -A -w

Additional Information

References:
Powered by Wolken Software