2025-05-07T05:15:51 [srm-reactive-thread-138] WARN com.vmware.srm.client.infrastructure.tasks.TasksFacade cc###b-b##3-####-####-##### - Task 'ManagedObjectReference: type = DR-UI-MANAGED-TASK, value = 0####4-8##5-####b0fd-######, serverGuid = 00000000-0000-0000-0000-000000000000' completed with error.(dr.storage.fault.CommandFailed) { faultCause = (dr.storage.fault.LocalizableAdapterFault) { faultCause = null, faultMessage = null, code = 7###-8c62-4b3d-#####-#######.1400, arg = null },faultMessage = null, commandName = discoverArrays 2025-05-07T05:15:51 [srm-reactive-thread-137] WARN com.vmware.dr.ui.tools.reactive.impl.PromiseImpl 66583######-20ab-####-adf8-####### getStorageDevices - Function 'com.vmware.srm.client.infrastructure.http.AsyncController$$Lambda/0x00007f68acefbb58@2cbb7284' failed.java.lang.IllegalStateException: The request associated with the AsyncContext has already completed processing. at org.apache.catalina.core.AsyncContextImpl.check(AsyncContextImpl.java:528) at org.apache.catalina.core.AsyncContextImpl.complete(AsyncContextImpl.java:91) at com.vmware.srm.client.infrastructure.http.AsyncController.lambda$start$2(AsyncController.java:141) at com.vmware.dr.ui.tools.reactive.impl.PromiseImpl$ApplyCompletion.complete(PromiseImpl.java:239) at com.vmware.dr.ui.tools.reactive.impl.PromiseImpl$Result.complete(PromiseImpl.java:41) at com.vmware.dr.ui.tools.reactive.impl.PromiseImpl$Completion.lambda$setResult$0(PromiseImpl.java:63):VMware Live Recovery 9.x
known_hosts file to establish a secure SSH connection.Cause Validation :
Validate host key verification failed error. If the keys are invalid or compromised, this needs to regenerate them on the storage system
Log path : /var/log/vmware/srm/dr.log
2025-05-07T05:15:51.088Z error vmware-dr[01522] [SRM@6876 sub=SraCommand opID=6bdc815b-71b1-###-##-####-reloadAdapters:cde3:cde3:3##:2445:###:c114:###:bf59:###:##6b] Command discoverArrays's stderr
--> Someone could be eavesdropping on you right now (man-in-the-middle attack)!
--> It is also possible that a host key has just been changed.
--> The fingerprint for the ECDSA key sent by the remote host is
--> SHA256:######L6##8U#####/ynT#########.
--> Please contact your system administrator.
--> Add correct host key in /home/srm/.ssh/known_hosts to get rid of this message.
--> Offending RSA key in /home/srm/.ssh/known_hosts:1
--> ECDSA host key for 10.###.##6.## has changed and you have requested strict checking.
--> Host key verification failed.
-->
2025-05-07T05:15:51.088Z verbose vmware-dr[01522] [SRM@6876 sub=SraCommand opID=###-###-44b6-####-a56971626316-reloadAdapters:cde3:3##:2445:###:c114:###:bf59:###:##6b] discoverArrays responded with:
--> <?xml version="1.0" encoding="UTF-8" ?>
--> <Response xmlns="http://www.vmware.com/srm/sra/v2">
--> <Error code="1220"/>
--> </Response>
Issue is not related to Site recovery Manager. Reach out to SRA Vendor and validate Docker Image ID associated with SRA because each SRA runs as a Docker container, and a Docker Image ID is assigned to it.