Why VM are not automatically add to a created rules

[P4thos]

Hi have a vCloud Usage Meter 3.4 running.

A rule has been created. This rule is set on a folder which contains VM. All the VM already present into the folder before the rule has been created have been added ( mapped ) into the rule

When I'm adding a new VM to that folder, this VM is not automatically added to the rules.

How to refresh the rules ?

Is there a way to automatically add the new VM in the rules ?

Regards.

[admin]

Use the "Re apply rules" option is the Rules tab view to push the new configuration.

[nicossl]

Good afternoon,

I have the same issue. I imported my customers and rules in the new release 3.4 and unfortunately any VMs is mapped.

Even by creating a new rule, the result is the same.

I have tried the "re apply rules" option but without success.

Thanks for your support.

[admin]

What is the object type, value type and value selected for the rules list?

[nicossl]

object type: Ressource Pool

value type: regular expression

value: (srv|wks)-a501-.*

This regular expression is working well in the previous release.

Thanks for your support.

[P4thos]

It seems working.

But is there a way to have this automated ?

I mean, I don't want to go and click on that button each time a VM is created or removed

[P4thos]

I had the same issue at the beginning.

To fix it, I have restarted the machine is which vUsage Meter is running

[nicossl]

restart the VM doesn't fix the issue unfortunately.

[admin]

Hi All,

We are aware of this issue in UM 3.4 with Object type as Resource pool and we are working to fix it in the upcoming release.

[nicossl]

Thanks for your feedback. When is planned this next release?

[admin]

Not sure, no ETA as of now.

[P4thos · Accepted solution]

As vCloud Usage Meter 3.4 is not anymore supported by VMWare, we moved to version 3.5 which is ok. Problem has been fixed with this version