VCF Installer Fails at "Deploy and Configure VCF Automation" Step Due to IP Conflict with Service CIDR
search cancel

VCF Installer Fails at "Deploy and Configure VCF Automation" Step Due to IP Conflict with Service CIDR

book

Article ID: 445085

calendar_today

Updated On:

Products

VMware SDDC Manager / VCF Installer VMware Cloud Foundation

Issue/Introduction

  • During the VCF installation process, the installer fails at the "deploy and configure VCF Automation"stage:


  • An error occurred in task: 
    Install Service Using Fleet lifecycle. See Tasks panel to learn more.
  • We get below error during the deployment:
    The Fleet lifecycle 'VSP component installation' task with ID [TASK_ID] failed. 
Internal errors: A pre-validation prevented the bootstrap: From the IPv4 pool, found the following in-use IP address(es): 10.#.#.240., Failed to bootstrap VCF services runtime of type 'CONSUMPTION'.
  • The domainmanager.log on SDDC Manager (/var/log/vmware/vcf/domainmanager/domainmanager.log) gives below error:
    Internal errors: A pre-validation prevented the bootstrap: From the IPv4 pool, found the following in-use IP address(es): 10.#.#.240., Failed to bootstrap VCF services runtime of type 'CONSUMPTION'., A pre-validation prevented the bootstrap: From the IPv4 pool, found the following in-use IP address(es): 10.#.#.240., Failed to bootstrap VCF services runtime of type 'CONSUMPTION'., A pre-validation prevented the bootstrap: From the IPv4 pool, found the following in-use IP address(es): 10.#.#.240., Failed to bootstrap VCF services runtime of type 'CONSUMPTION'., A pre-validation prevented the bootstrap: From the IPv4 pool, found the following in-use IP address(es): 10.#.#.240., Failed to bootstrap VCF services runtime of type 'CONSUMPTION'., A pre-validation prevented the bootstrap: From the IPv4 pool, found the following in-use IP address(es): 10.#.#.240., Failed to bootstrap VCF services runtime of type 'CONSUMPTION'., A pre-validation prevented the bootstrap: From the IPv4 pool, found the following in-use IPaddress(es): 10.#.#.240., Failed to bootstrap VCF services runtime of type 'CONSUMPTION'., A pre-validation prevented the bootstrap: From the IPv4 pool, found the following in-use IP address(es): 10.#.#.240., Failed to bootstrap VCF services runtime of type 'CONSUMPTION'., A pre-validation prevented the bootstrap: From the IPv4 pool, found the following in-use IP address(es): 10.#.#.240., Failed to bootstrap VCF services runtime of type 'CONSUMPTION'., A pre-validation prevented the bootstrap: From the IPv4 pool, found the following in-use IP address(es): 10.#.#.240., Failed to bootstrap VCF services runtime of type 'CONSUMPTION'.
        at com.vmware.vcf.vsp.services.fleetlcm.FleetLcmTaskExecutor.executeWithRetry(FleetLcmTaskExecutor.java:102)
        at com.vmware.vcf.vsp.services.fleetlcm.actions.InstallVspComponentFleetLcmAction.execute(InstallVspComponentFleetLcmAction.java:58)
        at com.vmware.vcf.vsp.services.fleetlcm.actions.InstallVspComponentFleetLcmAction.execute(InstallVspComponentFleetLcmAction.java:31)
        at com.vmware.evo.sddc.orchestrator.platform.action.FsmActionState.invoke(FsmActionState.java:66)
        at com.vmware.evo.sddc.orchestrator.platform.action.FsmActionPlugin.invoke(FsmActionPlugin.java:161)
        at com.vmware.evo.sddc.orchestrator.platform.action.FsmActionPlugin.invoke(FsmActionPlugin.java:147)
        at com.vmware.evo.sddc.orchestrator.core.ProcessingTaskSubscriber.invokeMethod(ProcessingTaskSubscriber.java:401)
        at com.vmware.evo.sddc.orchestrator.core.ProcessingTaskSubscriber.processTask(ProcessingTaskSubscriber.java:515)
        at com.vmware.evo.sddc.orchestrator.core.ProcessingTaskSubscriber.accept(ProcessingTaskSubscriber.java:128)
        at java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:103)
        at java.base/java.lang.reflect.Method.invoke(Method.java:580)
        at com.google.common.eventbus.Subscriber.invokeSubscriberMethod(Subscriber.java:85)
        at com.google.common.eventbus.Subscriber.lambda$dispatchEvent$0(Subscriber.java:71)
        at com.vmware.vcf.common.tracing.TraceRunnable.run(TraceRunnable.java:63)
        at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144)
        at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642)
        at java.base/java.lang.Thread.run(Thread.java:1583)
Collected the following errors for task with name InstallVspComponentFleetLcmAction and ID 0a#####d-9##d2-1##6-8##e-d####165: [ExecutionError [errorCode=null, errorResponse=LocalizableErrorResponse(messageBundle=com.vmware.evo.sddc.common.services.sddcman
agermessages)], ExecutionError [errorCode=null, errorResponse=LocalizableErrorResponse(messageBundle=com.vmware.evo.sddc.common.services.sddcmanagermessages)], ExecutionError [errorCode=null, errorResponse=LocalizableErrorResponse(messageBundle=com.vmware.evo.sddc.common.services.sddcmanagermessages)]]
DEBUG [c.v.e.s.o.c.ProcessingTaskSubscriber,dm-exec-1079]  Invoking task InstallVspComponentFleetLcmAction.UNDO, Plugin: VspServicesPlugin, ParamBuilder null, Input map: {componentSpec=DeployOrJoinVcfManagementComponents____24__DeployVcfAutomationFleetLcm____15__componentSpec}, Id:
  • In the deployment JSON, the vcfAutomationSpec and vspClusterSpec configurations show that the assigned IP addresses (e.g., 10.#.#.240) are within the defined gateway CIDR range (e.g., 10.#.#.1/24).

Environment

 VMware Cloud Foundation 9.x 

Cause

This issue occurs because the IP addresses allocated for the VCF Automation nodes or VSP cluster services reside within the CIDR range dedicated to the management network or internal cluster services. VCF pre-validation prevents bootstrapping if it detects that the IP addresses it intends to use for service runtimes are "in-use" or overlap with the defined network CIDR boundaries.

Resolution

To resolve this, ensure that all static IP addresses assigned to appliances and service pools are outside of the CIDR ranges dedicated to internal service runtimes or other overlapping network segments. Steps to fix:

  1. Open the deployment JSON configuration file used for the installation to redefine the CIDR Range.
  2. Locate the vcfAutomationSpec and vspClusterSpec sections. Update the allocated static IP addresses in the ipPool (for vcfAutomationSpec) and the ipv4Pool (for vspClusterSpec).  Ensure the newly assigned IP addresses do not fall within the subnet/CIDR range assigned to internal service runtimes or gateway boundaries (e.g., ensure they do not overlap with reserved internal gateway ranges like 10.#.#.1/24 or report as in-use).  
  3. Verify that the new IP addresses are completely free and unassigned on the management network using ping. Clear any cached pre-validation failure states in the Domain Manager engine to allow the pre-validation engine to re-scan the IPv4 pool without flagging the old IPs.
  4. Re-trigger the Failed Fleet Lifecycle TaskAccess the SDDC Manager UI or API. Navigate to the Tasks panel and select the failed task (Install Service Using Fleet lifecycle / InstallVspComponentFleetLcmAction).  
  5. Select Retry to restart the deployment workflow from the exact failure point using the updated JSON payload.
Powered by Wolken Software