-
Notifications
You must be signed in to change notification settings - Fork 930
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.
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
Missing osFamily attribute in Node definition causes command to fail #406
Comments
is there any output in the server log? |
Here is what I can find in rundeck.log
I'm not convinced it's useful, if needed I can change the log levels to have more details. |
can you post your node definition for the target node? |
oh I think I reproduced the issue. I think you are missing the When I removed the attribute from my node, I saw the same error. |
You are right, my machines seems to not have this attribute at all. I'll try to add it and see if it solves my issue. |
I can confirm adding this field fixed my issue. |
@rborer thanks |
When a job is defined with options, and a Command step tries to use the value of an option, the execution always fails.
For example (see screenshot), my job takes a parameter named goal, if I try to use it with ${option.goal} the job fails to execute at that step with the following error:
Here is the defined job:
The text was updated successfully, but these errors were encountered: