SRM collection fails if an SRM Protection Group has a VM in deleted status
search cancel

SRM collection fails if an SRM Protection Group has a VM in deleted status

book

Article ID: 322095

calendar_today

Updated On:

Products

VMware Aria Suite

Issue/Introduction

Symptoms:
The Usage Meter web application shows status for an added vCenter Server that its SRM collection has failed.
In SRM, one of its Protected Groups has a protected VM that is deleted, and this group shows a configuration error state when checked in SRM.

The Usage Meter appliance vccol_main.log shows the following error:
ERROR | ter collector thread |   com.vmware.um.vccollector.VCCollector | vCenter collector | SRM stage raised exception com.vmware.um.collector.CollectionError: SRM collection failed on server 30 failed due to Collection error: Unknown Failure Client received SOAP Fault from server: The object 'vim.VirtualMachine:vm-<UUID_1>' has already been deleted or has not been completely created Please see the server log to find more detail regarding the exact cause of the failure. :: https://<HOSTNAME>:443/drserver/vcdr/extapi/sdk


Environment

VMware vCloud Usage Meter 4.x

Cause

When a protected VM is removed from the vCenter inventory without removing its protection in SRM, Usage Meter throws a failed collection error after querying the SRM Protection Group. This results in partial SRM collection. This is expected behavior, and this scenario is resolved in Usage Meter 4.4.

Resolution



Workaround:

Procedure


To fix the SRM partial collection:
  1. In SRM, do one of the following:
  • Remove the affected VM from the Protection Group. Follow the steps here.
  • Remove the protection of the VM. Follow the steps described here.
  1. Ensure all Protection Groups have OK status.