Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

error handler has exception when attempting to handle No Matched Nodes failure for a job reference #350

Closed
gschueler opened this issue Apr 3, 2013 · 0 comments
Closed

error handler has exception when attempting to handle No Matched Nodes failure for a job reference #350

gschueler opened this issue Apr 3, 2013 · 0 comments
Assignees
@gschueler
Labels
bug
Milestone
1.5.1

Comments

@gschueler
Copy link
Member

when a job reference fails with "No nodes matched", the error-handler doesn't get triggered.

Output may look like:

10:40:11 [@  4-rundeck-jobref][SEVERE] No nodes matched for the filters: NodeSet{excludes={tags=taga, dominant=true, }, includes={tags=tagb, dominant=false, }}
10:40:11 [null@null null null][SEVERE] Could not find matching constructor for: com.dtolabs.rundeck.core.execution.workflow.steps.StepException(com.dtolabs.rundeck.execution.JobReferenceFailureReason, java.lang.String)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@gschueler gschueler

Labels
bug
Projects
None yet
Milestone
1.5.1
Development

No branches or pull requests
1 participant
@gschueler