2 Replies Latest reply on May 1, 2014 6:44 AM by mbrkic

getCustomFiled failing after upgrade to 5.5

mbrkic Apr 30, 2014 3:12 PM

Hi,

After upgrading Orchestrator to 5.5 I can no longer run the "getCustomField" action (nor the "Get Custom Attribute" workflow which calls that Action) successfully. I am getting the following error:

TypeError: Cannot read property "length" from undefined (Dynamic Script Module name : getCustomField#11)

After a short investigation it seems like VcVirtualMachine.vimHost.customFieldsManager.field is returning null (i.e., no custom attribute definitions are returned in the field array). If I browse through the mob tree for the same vCenter I can see the customFieldDef array without problems.

The vCenter is still at 5.1 and the vCO is now 5.5 and so is the vCenter plug-in.

Is anyone else seeing this?

Cheers,

Milos

1. Re: getCustomFiled failing after upgrade to 5.5

iiliev May 1, 2014 2:12 AM (in response to mbrkic)
Hi Milos,

Could you try to disable inventory service? We got numerous reports for inventory service returning incorrect data.

To disable it, put the following line in your vmo.properties file, and then restart vCO:
com.vmware.o11n.vim.useInventoryService=false

BTW, I think the inventory service will be deprecated in the future releases (if not already).

-Ilian
Like Show 0 Likes(0)

Actions
2. Re: getCustomFiled failing after upgrade to 5.5

mbrkic May 1, 2014 6:44 AM (in response to iiliev)

That seems to have done the trick.

Thank you!

Cheers,
Milos
Like Show 0 Likes(0)

Actions