Get metadata to update when DHCP changes (during create)

[smurawski]

No description provided.

[SympaHannuPiki]

Not 100% sure if this relates to same issue I have, but when I'm creating new Windows 2012 R2 Generation 1 VM with Windows 8.1 as a host, I do get wrong IP address. IP in metadata is having self assigned IP 169.xxx.xxx.xxx instead of IP from DHCP and when I'm looking VM itself and asking IP from Hyper-V, its IP is correctly fetched from DHCP (192.168.xxx.xxx). Server is created correctly, but rest of the process is failing obviously because it can't connect via WinRM with wrong IP address.

[smurawski]

@SympaHannuPiki Are you connecting the VM to a switch that has network access to the DHCP server? (sorry for the delayed reply - still catching up after being on the road the past month)

[SympaHannuPiki]

@smurawski, sorry for another long delay. Yes, switch has network access to the DHCP server and it's getting IP from it but maybe it's sometimes too late as it is getting internal IP assigned for Kitchen config instead of real IP that can be seen after Kitchen is done.

[gaelcolas]

This might be fixed since the above PR got merged. @SympaHannuPiki can you confirm or refute?
If fixed, this issue can be closed.
FWIW, I don't have the issue on Windows 10, even with a slow-ish DHCP.