Add host to vCenter workflow fails when cluster name contains non-ASCII characters

[panjl3]

We have a cluster that has a cluster name with Chinese character "王”， and it fails when we want to add a host to this cluster in vRO using the workflow in the picture below.

The Varialbes and logs of the failed run:

And we changed the cluster name "王" to "New Cluster", keep other info unchanged,  and it succeeded.

Any idea/clues will be very appricated! Or if verified that it's a issue , would it be fixed in the next version of vRO will be appriciated.

vRO appliance: 7.3.0.21553 build 5521409

[iiliev]

Could you check whether it works if you don't provide the resource pool input parameter?

[daphnissov]

Are non-ASCII characters even supported to begin with??

[panjl3]

Yes, it works if I don't choose resource pool. Does vRO currenltly not support using non-ASCII name cluster and with resource pool provided?

[iiliev]

It's not the vRO. If you look at scripting code of Add host to cluster workflow, you'll see that it is a thin wrapper around addHost_Task vCenter API, so it seems it's the vCenter API itself that rejects these characters.

[rmav01]

Might be a bit of a hail mary pass here, but if you were to do something like:

var clusterName = encodeURIComponent('王');

System.log(clusterName);

And use the encoded value set to clusterName as your input, I wonder if it would work. The hex value e7 8e 8b matches the UTF-8 value for 王:

Unicode/UTF-8-character table - starting from code position 7380

[iiliev]

The workflow uses cluster object instance instead of cluster name as a string, so encoding the name won't help.