vm conflict ip check is not compatible with Cloudstack based VPC

[cloudfoundry-community]

vm conflict ip check is not compatible with Cloudstack based VPC

[poblin-orange]

to clarify, bosh director has no issue with ip conflict between deployment.
This issue seem to be related to the ip check in the cpi. Convenient as it can identify ip conflict with zombie vm in a cloudstack zone. This control might be uncompatible with a cloudstack VPC configuration
Can u provide the error message your getting?

[dpassante]

You're right, the error message is sent by the IP-check done at the zone level in the CPI.

Error 100: java.lang.IllegalArgumentException: The required IP 192.168.6.17 is not available: used by vm cpivm-c7f87758-79bb-40d2-a8a6-c562b9e9756c.

It appears when an account tries to use the same ip address in multiples deployments, even if instances are provisioned on different VLAN.
This should affect any deployment done on ACS isolated network.

[poblin-orange]

A probable workaround to this issue is to use per VPC bosh account (so each cpi can only see the VPC network it manages) ?

[poblin-orange]

Fixed by searching conflicting vms only on the create_vm target network (so no conflict if same ip use on another network)

[poblin-orange]

delivered in v16