This is the error message
Request [5995f1ec-954c-4526-80f9-34ec3c914273]: Component [w2k16gui]: Network profile specified for the custom property VirtualMachine.Network0.NetworkProfileName does not exist.
I created a property definition called VirtualMachine.Network0.NetworkProfileName. I use a drop down list that contains three network profiles. All three are associated with my reservation. The names have not changed. For example. I have a network profile called DHCP. I am allowing the vRA IPAM Solution to manage the IP range but I did add in DNS etc. When I look at the profile I can drill down and see the existing VM's that I built previously. That profile is associated with a network on the Engineering reservation.
When the requestor selects the DHCP network the vNIC gets assigned to the DHCP network. Quick, eazy peazy.
I have upgraded vRA from 7.2 to 7.3 - in place upgrade
We have also migrated from a 6.0 vCenter to 6.5. - actual migration to a new vCenter.
I have verified the network profile settings along with the reservation. I have went as far as to delete the property definition and recreate it. I still get the same error.
Any thoughts would be great.
Did you get to fix this?.
I have a very similiar error but its on updating an existing blueprint so it won't allow me to publish the blueprint.
Like you trying to work out what's changed/broken as blueprint last changed 2 months ago and it worked then. I'm running 7.2.
to fix this error when trying to publish a blueprint:
remove the network profile property from the blueprint
create an empty custom property group
add the empty custom property group to the blueprint
publish the blueprint
add the network profile property to the property group "after" the blueprint is published to avoid the error during publishing.
if the request is failing during provisioning:
go to "Infrastructure"/"Reservations"/
click the reservation name (or however you like to get to "edit")
go to network tab
make sure the network is checked, and that the dropdown has the network profile selected.
This is a known issue in vRA 7.2, which has been fixed in 7.3. For vRA 7.2 there is a hotpatch. Unfortunately I'm not sure if I'm allowed to post it here, so you've better contact the GSS and open an SR for this issue.
If you already have an SR open, ask them to check this PR: 1793707 - in it they can find the link to the hotpatch and instructions how to install it.
Unless I am missing something in this thread, there is no such property VirtualMachine.Network0.NetworkProfileName
The correct property should be: VirtualMachine.Network0.ProfileName.
If I mis-read something then shoot me
Kindly refer the below links: