06-13-2019 07:54 AM
Is the current Infoblox plugin (o11nplugin-ipam.dar, InfobloxIPAM 18.104.22.1680079) is compatible with vRA/RO 7.5?
I am getting the following error when trying to run the vRO workflow "Setup Wizard". The error is "Property definition 'Infoblox.IPAM.createHostRecord' was not found." and the only thing I can find online searching is that there is a compatibility issue with 7.3 but I am unsure what version of the plugin that error was with. Unfortunately I can't revert to our current lab vRA/RO 7.5 so hoping I'm just missing an updated version of the plugin if this is the case?
Log extract from the workflow with failure entry.
[2019-06-12 11:30:44.677] [I] Registering IPAM Endpoint [2019-06-12 11:30:45.220] [I] Register IPAM Endpoint: Success [2019-06-12 11:30:51.007] [I] Workflow WFStubMachineProvisioned with ID 221 and revision 1 sent [2019-06-12 11:30:51.368] [I] The following properties have been passed: HashMap:1830590162 [2019-06-12 11:30:51.488] [I] Created menu operation with the name WFvCOMachineMenu1 [2019-06-12 11:30:52.133] [I] 145 [2019-06-12 11:30:53.120] [I] 224 [2019-06-12 11:30:53.492] [I] 99 [2019-06-12 11:30:53.801] [I] Created workflow with the name WFvCOMachineMenu1 [2019-06-12 11:30:54.569] [I] Property definition 'Infoblox.IPAM.createHostRecord' was not found. [2019-06-12 11:30:54.639] [E] Unable to create/update property definition: 403 (Dynamic Script Module name : addUpdatePropertyDefinition#31) (Dynamic Script Module name : addUpdatePropertyDefinition#36)
Solved! Go to Solution.
06-13-2019 08:19 AM
Plugin version 4.4.1 is compatible with vRA 7.5 (and 7.6, when used with the legacy vRO UI).
The log message about the missing property definition is not an error and is expected when running the setup workflow for the first time. If it had been attempted previously but failed for whatever reason, you may need to select the option to update the property group so that any missing properties can be added.
What is of concern is the error "Unable to create/update property definition: 403" This means that the operation was forbidden so if it continues to fail, you will want to verify that you are logged in with a user that has permissions to create these objects in vRA and in the tenant that you are operating in. This is where I would start with your troubleshooting efforts.
06-13-2019 08:35 AM
Regarding the 403 error, what permission would be the source of that problem? It's obviously able to communicate with the vra appliance (added endpoint) so im not sure what else to look into.
If it would help I could include the entire log output. I have the logs from the very first run and the follow up tests.
06-13-2019 09:19 AM
You can find details about permissions and roles here:
An account enabled as a tenant or fabric administrator should have sufficient privileges.
06-13-2019 10:35 AM
We used the firstname.lastname@example.org which is the default tenant/admin. I've not altered those permissions (not sure I could) from the first time install. From what I can tell it does have tenant admin.
I did some poking around trying to find where I might could alter the permissions but I couldn't find anyway to add it to "administrator" (when I did try it said that it was already in the group). After digging around I tried the workflow again to double check the log output and it worked... I am not sure why/how because far as I know I didn't change anything related to the administrator permissions but... I am not going to look a gift horse in the mouth with the time crunch I am in right now.
Thank you for your prompt and helpful response Tony.