Unable to assign IP to 2016 / 2019 servers using vRA8 Blueprint Deployment

[Atif_YNI]

I have the following setup:

1. vRA8

2. vSphere 6.7

I have several windows server 2016 templates. I have customization spec files that can assign an IP and add server to the domain.

I am using this template in a vRA8 Blueprint. The code is as such:

formatVersion: 1

inputs: {}

resources:

  Cloud_vSphere_Machine_1:

    type: Cloud.vSphere.Machine

    properties:

      image: W2K16DCE

      flavor: Large

      customizationSpec: W2K16 Standard

      networks:

        - network: '${resource.Cloud_vSphere_Network_1.id}'

  Cloud_vSphere_Network_1:

    type: Cloud.vSphere.Network

    properties:

      networkType: existing

      constraints:

        - tag: network:clientname

The machine gets deployed. Gets the right sizing. Connects to the correct port group. Then the customization begins. It reboots and takes 20 minutes and comes back with a 169.254.x.x IP and failed customization (name is changed but not added to domain).

I have created network profiles and assigned the tag network:clientname. I have assigned an IP range that is free and available. I can also deploy a VM from template using the same custom spec file and it works.

I am attaching customization spec log files from one of the VMs.

Any thoughts?

[stevedrummond · Accepted solution]

This has been answered in previous posts on Communities.

You need to tell vRA 8 you want a static IP assigned from the pool. Update your machine YAML:

networks:
     - network: '${resource.Cloud_vSphere_Network_1.id}'
       assignment: static

vRA 8 assumes DHCP so you must explicitly set static. Unfortunately you cannot configure it as a default for particular networks.

[Atif_YNI]

We found that this evening.

I tried searching on the forum for this issue but I was not able to find this resolution.

Thank you for taking the time to answer this.