-
Notifications
You must be signed in to change notification settings - Fork 229
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 server_max_queued_requests
and server_max_retry_delay
parameters
#570
Add server_max_queued_requests
and server_max_retry_delay
parameters
#570
Conversation
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.
This only works for Puppetserver >= 5.1, so there needs to be an added version check
784d87a
to
5e048c4
Compare
@baurmatt, the Redmine ticket used is for a different project than the one associated with this GitHub repository. Please either:
If changing the ticket number used, remember to update the PR title and the commit message (using This message was auto-generated by Foreman's prprocessor |
Yes of course -.- It should now be fixed. Edit: Not sure what @theforeman-bot wants from me :D |
@baurmatt, the Redmine ticket used is for a different project than the one associated with this GitHub repository. Please either:
If changing the ticket number used, remember to update the PR title and the commit message (using This message was auto-generated by Foreman's prprocessor |
We have the convention that #xxx refers to our Redmine issues while GH-xxx refers to Github issues. Could you amend the commit message to use that syntax? |
5e048c4
to
da3693c
Compare
Ah, yeah sure. Its fixed now :) |
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.
Other than the testing code (only mentioned once) it looks good.
) | ||
end | ||
it 'should have max-queued-requests: 0' do | ||
content = catalogue.resource('file', '/etc/custom/puppetserver/conf.d/puppetserver.conf').send(:parameters)[:content] |
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.
We have a verify_content
for this, or the regular expected.to contain_file('/etc/custom/...').with_content(/^ max-queued-requests: 0$/)
should work.
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.
I've just copied it from another test in this file, seems like there are a lot of options which are used in those tests ;) Switched to expected.to contain_file...
:)
This commit adds support for queueing and retrying requests if the Puppet Server is busy. https://puppet.com/docs/puppet/5.3/release_notes.html#new-feature-puppet-agents-can-retry-requests-on-a-configurable-delay-if-puppet-server-is-busy Fixes theforemanGH-569
da3693c
to
b4e211e
Compare
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.
The failure looks unrelated. I'm trying to tackle that in #573
merged, danke @baurmatt! |
This commit adds support for queueing and retrying requests if the Puppet
Server is busy.
https://puppet.com/docs/puppet/5.3/release_notes.html#new-feature-puppet-agents-can-retry-requests-on-a-configurable-delay-if-puppet-server-is-busy
Fixes GH-569