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

Add "Retry Passed Nodes" option similar to Retry Failed Nodes #4473

Closed
hs-hub-world opened this issue Feb 8, 2019 · 5 comments
Closed

Add "Retry Passed Nodes" option similar to Retry Failed Nodes #4473

hs-hub-world opened this issue Feb 8, 2019 · 5 comments

Comments

@hs-hub-world
Copy link

It would be great to have an option to Retry Passed Nodes..

image

Thank you!

@ahonor
Copy link
Contributor

ahonor commented Feb 8, 2019

@hs-hub-world interesting. Would you mind giving a use case as an example?

@hs-hub-world
Copy link
Author

Of course.
Some times we might scan for machines for particular file/process/attribute/etc.. and for those that failed because either Winrm was not configured or Powershell script simply failed, or the file/process was not found, etc.. but the script did succeeded on the some we would love to zoom in on the passed machines and run additional/other scripts to save time without hitting all the other/failed machines. Hope that makes sense.

@gschueler
Copy link
Member

@hs-hub-world do you mean you want to retry only on the successful nodes?

@hs-hub-world
Copy link
Author

hs-hub-world commented Jul 21, 2019

Hi @gschueler. Yes, that's correct. we should have the option to retry only on "successful" machines. For example, we might search for nodes that are running a specific process, once identified then we want to concentrate only on those nodes, the failed nodes should be ignored.

@stale
Copy link

stale bot commented Jul 20, 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 Jul 20, 2020
@stale stale bot closed this as completed Jul 22, 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

3 participants