vRA CloudClient issue: after reprovisioning a VM, the VM gets a new IP

[mkaetm]

Hi,

I am trying to reprovision a provisioned VM using the vRA CloudClient. Basically, reprovisioning works, but there is an annoying issue:

• - After being reprovisioned a new IP is assigned to the VM instead of using the already allocated IP

e.g. original allocated IP: 192.168.153.2

new IP after reprovisioning: 192.168.153.10 (instead of .153.2)

I executed the following command inside the vRA CloudClient:

CloudClient>vra machines action execute --id 'machinename' --action  Reprovision

I reviewed the request in the vRA portal and found out that properties like

• VirtualMachine.Network0.Address
• VirtualMachine.Network0.AddressType
• VirtualMachine.Network0.DnsSearchSuffixes
• VirtualMachine.Network0.DnsSuffix
• VirtualMachine.Network0.Gateway
• VirtualMachine.Network0.NetworkProfileName
• VirtualMachine.Network0.PrimaryDns
• VirtualMachine.Network0.SecondaryDns

are missing.

What am I doing wrong?

[z001yv0r]

I have similar issue,but after re-provisioning i have got the same IP Address.

But we are not able to reach the extrenal(NAT) IP Address from outside world after re-provisioning.

Do you use NSX or vCenter Distributed Switches & Portgroups??

Check the logs in vRA--> Infrastructure --> Recent Events tab..

We have below logs in our case!...

vCenter Orchestrator workflow Delete NAT Rules completed.

vCenter Orchestrator workflow Delete NAT Rules started.

vCenter Orchestrator workflow Remove secondary IP addresses assigned to Edge vNic completed.

vCenter Orchestrator workflow Remove secondary IP addresses assigned to Edge vNic started.

vCenter Orchestrator workflow Create NSX endpoint completed.

vCenter Orchestrator workflow Create NSX endpoint started.

[mkaetm · Accepted solution]

Hi,

we use vCenter Distributed Switches & Portgroups in our environment. I already checked the logs yesterday, but according to them everything is doing fine.

EDIT on 10/19/2016:

Finally, I was able to solve the problem. It's always a good idea to authenticate with the IaaS Host in case you want to grab IaaS components like network. Afterwards the reprovisioning process initiated through the CloudClient did exactly what I expected.

Now I'm able to script the CloudClient to automate the reprovisioning processes in our environment.

Anyhow, thanks for your support!