The vdsm logs are not the correct ones.
I assume this is the failure:
2020-02-04 22:04:53,631+05 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.MergeVDSCommand] (EE-ManagedThreadFactory-commandCoordinator-Thread-9) [1e9f5492-095c-48ed-9aa0-1a899eedeab7] Command 'MergeVDSCommand(HostName =
iondelsvr72.iontrading.com, MergeVDSCommandParameters:{hostId='22502af7-f157-40dc-bd5c-6611951be729', vmId='4957c5d4-ca5e-4db7-8c78-ae8f4b694646', storagePoolId='c5e0f32e-0131-11ea-a48f-00163e0fe800', storageDomainId='70edd0ef-e4ec-4bc5-af66-f7fb9c4eb419', imageGroupId='737b5628-e9fe-42ec-9bce-38db80981107', imageId='31c5e807-91f1-4f73-8a60-f97a83c6f471', baseImageId='e4160ffe-2734-4305-8bf9-a7217f3049b6', topImageId='31c5e807-91f1-4f73-8a60-f97a83c6f471', bandwidth='0'})' execution failed: VDSGenericException: VDSErrorException: Failed to MergeVDS, error = Drive image file could not be found, code = 13
please find the vdsm logs containing flow_id 1e9f5492-095c-48ed-9aa0-1a899eedeab7 and provide output for `vdsm-tool dump-volume-chains 70edd0ef-e4ec-4bc5-af66-f7fb9c4eb419` so we can see the status of the chain on vdsm
As well as `virsh -r dumpxml ind-co-ora-ee-02` (assuming ind-co-ora-ee-02 is the VM with the issue)
Changing the snapshot status with unlock_entity will likely work only if the chain is fine on the storage