Cannot upgrade VCF Automation from 9.0.2 to 9.1 due to IP address exhaustion in the management network block

Products

• VCF Automation

Issue/Introduction

• During an environment upgrade from VCF 9.0.2 to VCF 9.1, upgrading VCF Automation (VCFA) cannot proceed if there are fewer than 8 free IP addresses remaining within the current management block. The VCF user interface does not currently expose a native option to remove or un-deploy an unutilized VCFA 9.0.2 instance to change its network mapping.

Environment

 

• VMware Cloud Foundation Automation 9.x

• VMware Cloud Foundation Fleet 9.x

 

Cause

• This issue is caused by an architectural limitation within the VCFA 9.0.2 upgrade workflow, which mandates using the existing management network block allocation. While VCF 9.1 allows deploying VCF Automation to a non-management network, this capability is restricted to new installations and cannot be selected during an in-place upgrade when the source management network lacks free IP resources.

Resolution

This is resolved/updated  in Fleet Lifecycle 9.1.0.0400 and now you can mention an IP Range or IP's in comma separated format. 

Workaround

If your existing VCFA 9.0.2 instance contains no critical configuration or production data, you can perform a component cleanup and redeploy VCF Automation 9.1 directly to an alternate subnet:

1. Run the dedicated component cleanup script to remove the unutilized VCFA 9.0.2 instance from the deployment registry. For detailed instructions and to obtain the script, see Knowledge Base Article 441333.

2. After the cleanup script finishes successfully, initiate a fresh deployment of VCFA 9.1 onto your designated non-management network.

Additional Information

• Release Notes of Fleet lifecycle :
  https://techdocs.broadcom.com/us/en/vmware-cis/vcf/vcf-9-0-and-later/9-1/release-notes/patch-releases-9-1-0-x/vcf-operations/9-1-0-0400/fleet-lifecycle-9-1-0-0400-release-notes.html