-
Notifications
You must be signed in to change notification settings - Fork 118
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
Fixed calculation for Ansible playbook service max TTL. #193
Fixed calculation for Ansible playbook service max TTL. #193
Conversation
@miq-bot assign @gmcculloug |
@tinaafitz Please Review |
@billfitzgerald0120 Looks good. |
context "600 ttl, 100 retries eq interval 6" do | ||
let(:ae_retry_interval) { 6.minutes } | ||
let(:ttl) { 600 } | ||
context "650 ttl, 100 retries eq interval 6" do |
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.
Also need to update the "internal" value of the context.
context "600 ttl, 100 retries eq interval 6" do | ||
let(:ae_retry_interval) { 6.minutes } | ||
let(:ttl) { 600 } | ||
context "650 ttl, 100 retries eq interval 6" do |
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.
Same here.
84e4883
to
db4c6ef
Compare
@gmcculloug Made changes as requested, please review |
Checked commit billfitzgerald0120@db4c6ef with ruby 2.3.5, rubocop 0.47.1, and haml-lint 0.20.0 |
Fixed calculation for Ansible playbook service max TTL. (cherry picked from commit ae2736d) https://bugzilla.redhat.com/show_bug.cgi?id=1501524
Fine backport details:
|
Updated method and test.
https://bugzilla.redhat.com/show_bug.cgi?id=1497983
@miq-bot add_label bug, fine/yes