I am using vCD API to recompose empty vApp - adding a VM that is included in one of vApp templates. The template VM has one NIC currently.
The problem is that when this activity finish there is an alert generated on vCenter that the VM has a MAC address conflict. When I check the VM I can clearly see that new VM does not have duplicate MAC address. Also when I connect the VM to network and power it on - all is working fine, so this is quite annoying... Any ideas how to get rid of this behavior?
Here is the call...
POST "https://vcloud.fabric.sdi/api/vApp/vapp-89664ce3-ab9b-40f4-9af8-343d5ed178cb/action/recomposeVApp"
-H "Accept: application/*+xml;version=9.0"
-H "x-vcloud-authorization: 7c31d8acae6f4e30a392dde6a5a4fd5e"
-H "Content-Type: application/vnd.vmware.vcloud.recomposeVAppParams+xml;version=9.0"
<RecomposeVAppParams
name="Test vApp Gold"
xmlns="http://www.vmware.com/vcloud/v1.5"
xmlns:ovf="http://schemas.dmtf.org/ovf/envelope/1">
<Description>Test vApp</Description>
<InstantiationParams>
</InstantiationParams>
<SourcedItem>
<Source href="https://vcloud.fabric.sdi/api/vAppTemplate/vm-ce6c8c30-818b-4f5a-90f6-6dc5d826486d"/>
<VmGeneralParams>
<Name>AppServer-01a</Name>
<Description>Internal Access</Description>
<NeedsCustomization>true</NeedsCustomization>
</VmGeneralParams>
<StorageProfile href="https://vcloud.fabric.sdi/api/admin/vdcStorageProfile/3da9fdbb-0382-464c-8623-1902cd4e66d5">
</StorageProfile>
</SourcedItem>
<AllEULAsAccepted>true</AllEULAsAccepted>
</RecomposeVAppParams>