Cloud Foundry deployment fails because of IP address conflicts

Cloud Foundry deployment fails because of IP address conflicts.

Symptoms

During the create virtual machine (VM) stage of the Cloud Foundry deployment, an error similar to the following message is displayed:

11:52:30 | Compiling packages: tps/ef9adb86728a43959bd8c3549106f7582513a294 (00:00:06)
            L Error: Unknown CPI error 'Unknown' with message 'Detected IP conflicts with other VMs on the same networks: tools-vm01 on network VM Network with ip 172.16.215.160' in 'create_vm' CPI method..................

Resolving the problem

Open your vCenter instance and search to see whether a VM already uses the IP address that was displayed in the error message. A VM that is not part of your IBM Cloud Private Cloud Foundry deployment might use the IP address.
If the IP address is in use, determine whether it is used by a VM that is part of your IBM Cloud Private Cloud Foundry deployment. If the VM name starts with the vm- prefix, it is part of your IBM Cloud Private Cloud Foundry deployment.
Correct the problem.
- If the VM is not part of your IBM Cloud Private Cloud Foundry deployment, then the subnet or address_range that you specified during IBM Cloud Private Cloud Foundry installation contains VMs. Determine subnet and address_range values that you reserve for IBM Cloud Private Cloud Foundry and update your IBM Cloud Private Cloud Foundry installation. See Installing IBM® Cloud Private Cloud Foundry.
- If the VM is part of your IBM Cloud Private Cloud Foundry deployment and the error did not occur during the compilation phase, you might need to clean your VMware resource pool. If you restarted deployment by deleting the data directory, the VMs that are created during installation might not be removed. Clear the resource pool and run the deployment again.
- If the VM is part of your IBM Cloud Private Cloud Foundry deployment and the error occurred during the compilation phase, contact IBM support.