An extra IP address is allocated from the IP pool when you move or copy a vApp template between catalogs
search cancel

An extra IP address is allocated from the IP pool when you move or copy a vApp template between catalogs

book

Article ID: 328220

calendar_today

Updated On:

Products

VMware

Issue/Introduction

Symptoms:
An extra IP address is allocated from the IP pool when you move or copy a vAPP template between catalogs. This causes a duplicate IP address issue when using VMware vCloud Director REST API to deploy from it.

Cause

Resolution

This is a known issue affecting VMware vCloud Director v5.5.1.x and VMware vCloud Director v5.5.2.x.

This issue is resolved in VMware vCloud Director 5.5.3, available at VMware Download Center.
To work around this issue, redeploy the copied/moved vAPP template using the VMware vCloud Director web UI and then recapture it to catalog as a new template. This removes the assigned IP address.


Additional Information

Steps to reproduce this issue:
  1. Build a vApp with one or more virtual machines. Ensure the virtual machines NIC is connected to an org vCloud Director network by selecting static IP pool.
  2. Capture this vApp to catalog by choosing the customize settings option.
  3. Check the virtual machine in the captured vApp template to verify that the NIC is connected to the org network without an IP address.
  4. Move or copy this vApp to another catalog in the same org and verify that the virtual machine template has a new IP address allocated from the pool.

    Note: The expected behavior is that the vAPP template should keep the same setting and not have an IP address allocated.

  5. If you deploy this moved vApp template to MyCloud using the vCloud Director Web UI, another new IP address from the IP pool is allocated

    When you deploy the vApp of the moved template using an API call, you see the error:

    The following IP/MAC addresses have already been used by running virtual machine.


Powered by Wolken Software