VMware Cloud Community
DaweBartos
Contributor
Contributor

vCD API recomposeVApp - adding VM creates MAC conflict alarm on vCenter

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>

Reply
0 Kudos
9 Replies
Sreec
VMware Employee
VMware Employee

Haven't seen such issues so far.But curious to know if output is same if we deploy this VM via GUI ? Please test it via GUI based deployment and let me know if alarms are still generating.

Cheers,
Sree | VCIX-5X| VCAP-5X| VExpert 6x|Cisco Certified Specialist
Please KUDO helpful posts and mark the thread as solved if answered
Reply
0 Kudos
qc4vmware
Virtuoso
Virtuoso

We run into the same thing in our environment fyi.

Reply
0 Kudos
DaweBartos
Contributor
Contributor

To be honest I had never tried this before:) however yes this happens also when doing such activity via GUI (tried on vCD v8.0 / 8.0.1, no matter what OS), I create empty vApp and then I add a VM from vApp template to it. vCenter then produces the alarm again. The only way how to get around this I think currently is to remove that one NIC the template VM has attached, but it then complicated eg. patching procedures of the template since we probably need to add that NIC before patching then do patching of the template and remove it again before putting template back to prod.

Reply
0 Kudos
DaweBartos
Contributor
Contributor

Do you think this may be considered a bug or is it an expected behavior?

Reply
0 Kudos
Sreec
VMware Employee
VMware Employee

I was able to reproduce MAC conflict scenario and most likely you would have done same thing. When you imported the VM to your catalog,you would have selected "Make Identical Copy" and other option is "Customize VM".Assuming that you have selected "Make Identical Copy" and when you try to deploy the VM from catalog via API it will have same settings as source VM and MAC address duplicate is expected.Results would be same if you try this via GUI also.Try this in GUI and you will get a message "Any VMs requiring network interfaces in this vApp may be created using duplicate MAC addresses" in the GUI.Since you have tried this via API it wont even show the message before deployment "Any VMs requiring network interfaces in this vApp may be created using duplicate MAC addresses". API wont give any proactive warning,if the syntax is right it will execute the query or it will fail Smiley Happy 




Cheers,
Sree | VCIX-5X| VCAP-5X| VExpert 6x|Cisco Certified Specialist
Please KUDO helpful posts and mark the thread as solved if answered
Reply
0 Kudos
AshleyBanks
Contributor
Contributor

I know its an old post but took me a while to find VMware's very unhelpful answer.

Duplicate MAC address alarms are present when a VM is deployed in vCloud Director

Reply
0 Kudos
mjha
Hot Shot
Hot Shot

This is not problem with vCD. Its issue with vSphere 6.0.

Last I heard from vSphere engineering team that this issue is fixed in vSphere 6.0 U3

Please consider marking this answer "correct" or "helpful" if you think your query have been answered correctly. Manish Jha | Operations Support Engineer | vCloud Air Operations vExpert 2015-17 | vExpert-NSX | vExpert-Cloud | VCAP6-DCV | VCP6-DCV | RHCE-7 Website : http://vstellar.com
Reply
0 Kudos
qc4vmware
Virtuoso
Virtuoso

This has been an issue for as long as I can remember... I've also heard it has been fixed many times but seemed to persist.  Maybe 6.0 U3 does fix it but I can't confirm as all of our vCD is at a lower version.

Reply
0 Kudos
don613
Contributor
Contributor

My vCenter Server is 6.0 Update 3b and I had the same issue.

I just disabled that Alarm.

Reply
0 Kudos