Greatly appreciate this forum for the support and knowledge sharing! I have got another question around this vRA / vRO 7.3 Integration of Infoblox IPAM.
If I try with below properties, "Update" workflow fails with "Unable to update host record".
Error Message: [E] (com.infoblox.ipam.vcac.util/throwIpamError) Error in (Dynamic Script Module name : throwIpamError#28) IPAM Provider Error: {"code":3000,"message":"Unable to update host record: no host records were found in IPAM. (Workflow:Update vNIC / Get unique record (item10)#1)"}
[E] Workflow execution stack:
***
item: 'Update/item7', state: 'failed', business state: 'null', exception: 'IPAM Provider Error: {"code":3000,"message":"Unable to update host record: no host records were found in IPAM. (Workflow:Update vNIC / Get unique record (item10)#1)"} (Dynamic Script Module name : throwIpamError#28)'
workflow: 'Update' (712f2f72-701d-459a-84f5-4bbec0cbd5cc)
| 'attribute': name=attrErrorMessage type=string value=Unable to update host record: no host records were found in IPAM. (Workflow:Update vNIC / Get unique record (item10)#1)
| 'attribute': name=attrIpamConnection type=InfobloxIPAM:IpamConnection value=dunes://service.dunes.ch/CustomSDKObject?id='InfobloxETLab'&dunesName='InfobloxIPAM:IpamConnection')
Please share any thoughts and experiences you had with this integration and any helpful insight on how to successfully integrate/ recommendations/ suggestions are appreciated!
Any response or direction is appreciated!
Hey,
Any luck with this? I'm kind of going through a similar situation. I'm trying to use some 3rd party custom hostname plugin and get Infoblox to update the hostname. I'm thinking of using the "Update" workflow and I created an event subscription for it, but I always get a "vRA VM is not initialized!" error.
Were you ever able to get this to work to update a DNS record using your custom hostname?
Check to see if the host record you are trying to create exists, and if so, does the account have permissions to that record. That's what i typically see when i get the 3000 error message.
I recently had a similar error during a deployment of a Windows VM. Turned out is was caused by the DNS registration of the VM itself. See my post on this.