VRA 8.3 "AutoConfigurer" cleans up resource?

[michaelbachmann]

Dear Community,

Does anyone know, why vRa is automatically cleaning up resources? 

We have never seen this user nor this behavior before.
The machine from this deployment still exists in vCenter but is not in vRa anymore.

If this is possible, it should also be possible to unregister a machine, right?

[maverix7]

The AutoConfigurer's job is to keep in sync the state of the compute resource with the state of the deployment. So if it finds out that a compute resource (VM) is missing, it will remove it from the deployment, with the history entry that you show in your screenshot. It will never actually destroy the resource!

Now... there are 2 situations in which it can think that a VM has gone missing:
1. It was removed by 3rd party system/person directly from the endpoint (vSphere) - expected
2. There is some issue with enumeration, or some other issue that is falsely reporting that the VM is missing - bug

In your case it seems like it is 2., so I would suggest you open an SR

[michaelbachmann]

Alright, I have already suspected that. In our case it is because the machine was moved to another endpoint....

Do you know if this is a scheduled task or does it work ad-hoc?

Is it possible to manually trigger this action?