Custom workflow failing with "No such host is known" error in OnCommand Workflow Automation
- Views:
- 171
- Visibility:
- Public
- Votes:
- 3
- Category:
- oncommand-workflow-automation-wfa
- Specialty:
- legacy
- Last Updated:
Applies to
OnCommand Workflow Automation (WFA) 4.x, 5.x
Windows 2012
Issue
Custom workflow is failing with below error
2021-03-13 21:21:19,357 ERROR [com.netapp.wfa.job.backend.JobsExecutionInterceptor] (Thread-1868 (ActiveMQ-client-global-threads)) Job CacheJob{, dataSourceId=DataSourceInfo{id=21, name='ds_name', connectionDetails=ConnectionDetails{id=21, ip='x.x.x.x', port=8080, userName='wfa', password='******', databaseName='null', timeoutInMinutes=10, lastUpdateTime=0}, dataProviderType=DataProviderType{id=16, productType='snapshots', productVersion='OCUM 7.x', scheme='snapshots'}}, schemeId=Scheme{id=8, name='snapshots'}, dataSourceName='ds_name', schemeName='snapshots'} failed: com.netapp.wfa.cache.execution.CacheException: Error running data acquisition script: Exception calling "Connect" with "2" argument(s):
"No such host is known"