VMware Cloud Community
mbrkic
Hot Shot
Hot Shot
Jump to solution

getCustomFiled failing after upgrade to 5.5

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

Reply
0 Kudos
1 Solution

Accepted Solutions
iiliev
VMware Employee
VMware Employee
Jump to solution

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

View solution in original post

Reply
0 Kudos
2 Replies
iiliev
VMware Employee
VMware Employee
Jump to solution

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

Reply
0 Kudos
mbrkic
Hot Shot
Hot Shot
Jump to solution

That seems to have done the trick.

Thank you!

Cheers,

Milos

Reply
0 Kudos