Whats the max size of a VM affinity rule?

[mccarthybri]

Getting an error on creating a VM affinity rule, saying the rule is too long. Does anybody know what the limit is? This rule is for 4 VMs with names of about 15 characters each. Seems like a low limit

[Sateesh_vCloud]

Can you share error screenshot?

[mccarthybri]

The error reads 'HA group affinity for nviet_vsim_mc4n1,nviet_vsim_mc4n2,nviet_vsim_mc4n3,nviet_vsim_mc4n4' is invalid or exceeds the maximum number of characters permitted.

[Sateesh_vCloud]

From the error:

You are trying to create host group with four servers. What is the group name that you are giving?

Is it like server1,server2,server3,server4?  (If so can you change it to 4HOSTS and try to create once again?)

[vThinkBeyondVM]

It seems you are trying to create VM-VM affinity rule. Can you please let us know what is the rule name? Try giving meaningful name with less characters.

There is other possibility that you are creating VM group for VM-Host affinity rule. Plz give vm group name with less characters & see if that works

Not sure on char limit but for VM name its 80 char. I never come across this issue while creating rule, I will dig on rule name limit and get back to you.

[mccarthybri]

I realized after posting that the complaint was about the length of the name. The problem here is that I need to dynamically generate

a [or potentially many] unique rule names. I think I have a way to make them shorter., so that should work.

However, It appears (I haven't tried the 4 node case directly yet, Our QA guys saw it) that the behavior is as follows. I create the rule (through

the perl API). The modify cluster config reports no error, the rule (with the oversized name) is kept, and ignored. This was noticed because the

VMs started on different hosts. Only when examining the cluster rules in the GUI did it show the "too long" issue.