Execution fails on new installation project with script resource model source

[kristian-lesko]

Issue type: Bug report My Rundeck detail

• Rundeck version: 2.7.3-1
• install type: WAR
• OS Name/version: CentOS 7.3

Expected Behavior When Rundeck is installed and a project is defined with a script Resource Model Source, we expect it to be able to run a job in this project right away, loading the execution nodes from the resource model source.

Actual Behavior When a job is executed in a project after setup as described above, the execution fails with the following error:

com.dtolabs.rundeck.core.NodesetEmptyException: No matched nodes: NodeSet{includes={name=sample-node, dominant=false, }} at com.dtolabs.rundeck.core.execution.workflow.NodeFirstWorkflowExecutor.validateNodeSet(NodeFirstWorkflowExecutor.java:350) at com.dtolabs.rundeck.core.execution.workflow.NodeFirstWorkflowExecutor.executeWorkflowImpl(NodeFirstWorkflowExecutor.java:88) at com.dtolabs.rundeck.core.execution.workflow.BaseWorkflowExecutor.executeWorkflow(BaseWorkflowExecutor.java:317) at com.dtolabs.rundeck.core.execution.WorkflowExecutionServiceThread.run(WorkflowExecutionServiceThread.java:55) Exception: class com.dtolabs.rundeck.core.NodesetEmptyException: No matched nodes: NodeSet{includes={name=sample-node, dominant=false, }} No matched nodes: NodeSet{includes={name=sample-node, dominant=false, }}

However, it seems that even though this execution fails, the nodes are loaded from the script source properly, and the second execution works as expected.

How to reproduce Behavior

• Install Rundeck
• Setup a project with a script Resource Model Source that defines some nodes
• Create a job that executes on one of the defined nodes
• Run the job

[fdevans]

Somehow this bug got buried in our Docs project. If this is still an issue on the current version of Rundeck please feel free to open a new issue in the rundeck/rundeck project.