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.

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

failOnDisable true on job step missing on uploaded job #3495

Closed
h-haaks opened this issue Jun 7, 2018 · 1 comment
Closed

failOnDisable true on job step missing on uploaded job #3495

h-haaks opened this issue Jun 7, 2018 · 1 comment

Comments

@h-haaks
Copy link

h-haaks commented Jun 7, 2018

Describe the bug
We have just upgraded to Rundeck 2.11.3-1 and found some of our jobs just silently ignored job steps refering disabled jobs.

We found the option "Fail on disabled execution?" and enabling solves this :)

Our problem now is that this setting does not seem to be implemented on upload of yaml or by using 'rd jobs load' ...

My Rundeck detail

  • Rundeck version: 2.11.3
  • install type: deb
  • OS Name/version: Debian 9 ( Docker )
  • DB Type/version: none?

To Reproduce
Steps to reproduce the behavior:

  1. Create a job with command step "echo 'hey'"
  2. Create a second job with job step ref 1. job, and select "Fail on disabled execution?"
  3. Download job definition in yaml
  4. Delete second job
  5. Upload the downloaded definition
  6. "Fail on disabled execution?" is not selected ...

Expected behavior
Download followed by upload should keep the same job definition.

Desktop (please complete the following information):

  • OS: Windows 10
  • Browser chrome
  • Version 66.0.3359.181
@h-haaks h-haaks changed the title failOnDisable true on job task missing on uploaded job failOnDisable true on job step missing on uploaded job Jun 7, 2018
@stale
Copy link

stale bot commented Apr 3, 2020

In an effort to focus on bugs and issues that impact currently supported versions of Rundeck, we have elected to notify GitHub issue creators if their issue is classified as stale and close the issue. An issue is identified as stale when there have been no new comments, responses or other activity within the last 12 months. If a closed issue is still present please feel free to open a new Issue against the current version and we will review it. If you are an enterprise customer, please contact your Rundeck Support to assist in your request.
Thank you, The Rundeck Team

@stale stale bot added the wontfix:stale label Apr 3, 2020
@stale stale bot closed this as completed Apr 5, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant