BugZero updated this defect 44 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
4/5/2024
Site Recovery Manager
8.58.3
No fixed releases provided.
You are unable to reconfigure SRM Appliance after upgrade ERROROperation FailedHost 'esxi02.vmware.local' could not be contacted.Operation ID: 1bf65fa3-90b3-412a-886d-e2113d265d163/20/21, 2:01:29 PM +0000/var/log/vmware/srm/drconfig.log: 2021-03-20 14:01:29,699 [srm-reactive-thread-15] WARN com.vmware.dr.configservice.taskMonitor.ConfigureTaskHandler 1bf65fa3-90b3-412a-886d-e2113d265d16 getConfigureTaskProgress - Task finished with error! (drConfig.fault.HostUnreachableFault) { faultCause = null, faultMessage = null, address = esxi02.vmware.local port = 443, errorDescription = Fault cause: vmodl.fault.SystemError } at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:423) at java.lang.Class.newInstance(Class.java:442) at com.vmware.vim.vmomi.core.types.impl.ComplexTypeImpl.newInstance(ComplexTypeImpl.java:174) at com.vmware.vim.vmomi.core.types.impl.DefaultDataObjectFactory.newDataObject(DefaultDataObjectFactory.java:25) at com.vmware.vim.vmomi.core.soap.impl.unmarshaller.ComplexStackContext.<init>(ComplexStackContext.java:30) at com.vmware.vim.vmomi.core.soap.impl.unmarshaller.StackContextFactory.newContext(StackContextFactory.java:113) at com.vmware.vim.vmomi.core.soap.impl.unmarshaller.FaultStackContext.getNestedContext(FaultStackContext.java:86) at com.vmware.vim.vmomi.core.soap.impl.unmarshaller.UnmarshallerImpl$UnmarshallContext.beginElement(UnmarshallerImpl.java:365) at com.vmware.vim.vmomi.core.soap.impl.unmarshaller.UnmarshallerImpl$UnmarshallContext.parse(UnmarshallerImpl.java:274) at com.vmware.vim.vmomi.core.soap.impl.unmarshaller.UnmarshallerImpl$UnmarshallContext.parse(UnmarshallerImpl.java:227) at com.vmware.vim.vmomi.core.soap.impl.unmarshaller.UnmarshallerImpl$UnmarshallContext.unmarshall(UnmarshallerImpl.java:210) at com.vmware.vim.vmomi.core.soap.impl.unmarshaller.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:80) at com.vmware.vim.vmomi.core.soap.impl.unmarshaller.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:74) at com.vmware.vim.vmomi.client.common.impl.ReturnvalStackContext.setValue(ReturnvalStackContext.java:45) at com.vmware.vim.vmomi.client.common.impl.ResponseUnmarshaller.processNextElement(ResponseUnmarshaller.java:127) at com.vmware.vim.vmomi.client.common.impl.ResponseUnmarshaller.unmarshal(ResponseUnmarshaller.java:70) at com.vmware.vim.vmomi.client.common.impl.ResponseImpl.unmarshalResponse(ResponseImpl.java:284) at com.vmware.vim.vmomi.client.common.impl.ResponseImpl.setResponse(ResponseImpl.java:231) at com.vmware.vim.vmomi.client.http.impl.HttpExchangeBase.parseResponse(HttpExchangeBase.java:236) at com.vmware.vim.vmomi.client.http.impl.HttpAsyncExchange$1$2.invokeWithinScope(HttpAsyncExchange.java:168) at com.vmware.vim.vmomi.client.http.impl.TracingScopedRunnable.run(TracingScopedRunnable.java:24) at com.vmware.dr.ui.tools.utilities.ThreadContext.lambda$wrap$10(ThreadContext.java:55) at com.vmware.dr.ui.tools.utilities.ThreadContext.execute(ThreadContext.java:209) at com.vmware.dr.ui.tools.utilities.ThreadContext.execute(ThreadContext.java:185) at com.vmware.dr.ui.tools.utilities.ThreadContext.setupContext(ThreadContext.java:76) at com.vmware.dr.ui.tools.utilities.ThreadContext.setupContext(ThreadContext.java:105) at com.vmware.dr.ui.tools.utilities.ExecutorUtils.lambda$wrap$6(ExecutorUtils.java:36) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748)
Remove com.vmware.vcDr from vCenter MOB. Refer to https://kb.vmware.com/s/article/1025360 for removal steps.
Remove SRM and vSphere Replication extensions from the MOB and register again. Only remove the extension of the appliance that is failing to register. com.vmware.vcHms com.vmware.vcDr You might run in to the same issue after repointing the VC to a different sso domain - but SRM server did not log anything in /var/log/vmware/srm/drconfig.log,