Hello,
Our users reported many of their jobs fail to run when scheduled with the following error…
com.dtolabs.rundeck.core.NodesetEmptyException: No matched nodes: NodeSet{includes={hostname=node_fqdn.tld, dominant=false, }}
at com.dtolabs.rundeck.core.execution.workflow.BaseWorkflowExecutor.validateNodeSet(BaseWorkflowExecutor.java:880)
at com.dtolabs.rundeck.core.execution.workflow.NodeFirstWorkflowExecutor.executeWorkflowImpl(NodeFirstWorkflowExecutor.java:92)
at com.dtolabs.rundeck.core.execution.workflow.BaseWorkflowExecutor.executeWorkflow(BaseWorkflowExecutor.java:220)
at com.dtolabs.rundeck.core.execution.WorkflowExecutionServiceThread.runWorkflow(WorkflowExecutionServiceThread.java:95)
at com.dtolabs.rundeck.core.logging.LoggingManagerImpl$MyPluginLoggingManager.runWith(LoggingManagerImpl.java:146)
at com.dtolabs.rundeck.core.execution.WorkflowExecutionServiceThread.run(WorkflowExecutionServiceThread.java:77)
Exception: class com.dtolabs.rundeck.core.NodesetEmptyException: No matched nodes: NodeSet{includes={hostname=node_fqdn.tld, dominant=false, }}
No matched nodes: NodeSet{includes={hostname=node_fqdn.tld, dominant=false, }}
This error doesn’t make sense in this case as the node specified in the job’s filter actually exists in the project’s nodes list and should match.
The same job from the same project with the same filter works just fine when it’s run manually. This bug happens only some jobs are scheduled.
Has anyone experienced the same issue and found any solution or at least a workaround ?