-
Notifications
You must be signed in to change notification settings - Fork 897
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
Honor user provided execution_ttl option #17476
Conversation
Checked commit bzwei@bfb3c7a with ruby 2.3.3, rubocop 0.52.1, haml-lint 0.20.0, and yamllint 1.10.0 |
@tinaafitz please review |
@miq-bot add_label blocker |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@bzwei Looks good.
@mkanoor Please review. |
Honor user provided execution_ttl option (cherry picked from commit 75cbaf4) Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1583851
Gaprindashvili backport details:
|
PlaybookRunner
is a subclass ofJob
. Previously it depends onJob
DEFAULT_TIMEOUT
which equals 5 minutes. If the playbook does not complete before this timeout, it gets abort.PlaybookRunner
already takes optionexecution_ttl
in minutes from user when the automate playbook method is defined. This number is now used to overridecurrent_job_timeout
method. If this option is not given a new default 10 minute is used instead.fixes https://bugzilla.redhat.com/show_bug.cgi?id=1581465