When attempting to upgrade VCF Automation (VCF-A) to version 9.1.x, the configuration precheck fails with a CIDR validation error, even if individual IP addresses have been provided in the UI.
Error Message:
An unexpected error occurred in stepvalidate_vsp_cluster_input. Reference Code: ########.
Detail:com.broadcom.vcf.lcm.sddc.upgrade.plugin.shared.step.io.ValidateVspClusterInputStepInputfailed validation. [ConstraintViolationImpl{interpolatedMessage='Target VSP cluster IP pool CIDR is required', propertyPath=targetVspClusterIpPoolCidr, rootBeanClass=class com.broadcom.vcf.lcm.sddc.upgrade.plugin.shared.step.io.ValidateVspClusterInputStepInput, messageTemplate='Target VSP cluster IP pool CIDR is required'}]
VCF Automation (formerly Aria Automation)
In VMware Cloud Foundation releases prior to 9.1.0.0400, the VCF Automation upgrade orchestration framework strictly required a contiguous /29 CIDR block for network initialization.
Starting with version 9.1.0.0400 (Fleet Lifecycle Patch), the product added the ability to use a single IP range (individual IP addresses) instead of a strict CIDR block. However, if the supporting lifecycle components are not updated to the required versions, the precheck validation logic will continue to enforce the legacy CIDR requirement.
Update underlying lifecycle management components to enable individual IP address input during the VCF upgrade precheck.
Update the components in the following order:
validate_vsp_cluster_input step should now pass without requiring a CIDR block.