-
Notifications
You must be signed in to change notification settings - Fork 898
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 job_timeout parameter for upgrade_cluster #18230
Add job_timeout parameter for upgrade_cluster #18230
Conversation
The motivation here is that we need the job to have one timeout, and the Ansible role to have another - the job will end if the timeout from the time it was created will pass, while Ansible playbook will only timeout if it is stack for too long on one phase. So we will want to set the job timeout to something huge - 1 year, and set a real timeout through the playbook extra_vars. This is part of implementing: https://bugzilla.redhat.com/show_bug.cgi?id=1644605
@agrare I think this is the last one for this phase of the cluster upgrade. |
Checked commit borod108@e1965d6 with ruby 2.3.3, rubocop 0.52.1, haml-lint 0.20.0, and yamllint 1.10.0 |
@borod108 is there a corresponding PR to manageiq-providers-ovirt to accept and set |
@agrare I do not think that is required. https://github.com/ManageIQ/manageiq-providers-ovirt/blob/master/app/models/manageiq/providers/redhat/ansible_role_workflow.rb
|
Forgot that you already did that here https://github.com/ManageIQ/manageiq/pull/18108/files#diff-a8d27c2744e902e4796e24bb1560aec7R6 👍 |
@borod108 if this is the last part needed for backporting this feature lets get on the migration for STI for the other infra providers so we can get this moved to ovirt. |
@miq-bot add-label hammer/yes |
Add job_timeout parameter for upgrade_cluster (cherry picked from commit 0e1006b) https://bugzilla.redhat.com/show_bug.cgi?id=1644605
Hammer backport details:
|
The motivation here is that we need the job to have one timeout, and the
Ansible role to have another - the job will end if the timeout from the
time it was created will pass, while Ansible playbook will only timeout if it is
stack for too long on one phase. So we will want to set the job timeout
to something huge - 1 year, and set a real timeout through the playbook
extra_vars.
This is part of implementing: https://bugzilla.redhat.com/show_bug.cgi?id=1644605