This issue will be resolved in a future release of vRealize Operations.
Workaround:
To workaround this issue, restart the CaSA service on the Primary and Replica (if applicable) nodes.
- Log into the Primary node as root via SSH or Console, pressing ALT+F1 in a Console to log in.
- Run the following command to restart the CaSA service:
systemctl restart vmware-casa
- Repeat steps 1-2 on the Replica node (if applicable).