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
fixes #10489 - adding two timeouts for content tasks #5225
Conversation
requires Dynflow/dynflow#151 |
@@ -35,6 +35,9 @@ common: | |||
redhat_repository_url: https://cdn.redhat.com | |||
consumer_cert_rpm: 'katello-ca-consumer-latest.noarch.rpm' | |||
|
|||
content_action_accept_timeout: 20 #in seconds | |||
content_action_finish_timeout: 3600 #in seconds |
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.
What about making these admin configurable settings as opposed to ones that require server restart?
The first will fail the task if the client does not pick up the task this likely means that either the client is not running, goferd is not running, or goferd is having some sort of communication issue. (Default 20 seconds) The second will fail if the client has picked up the task but has not completed it after some time. This could happen if the link is really really slow, or the client dies in the middle of a content action. (Default to 60 minutes)
19b1a5b
to
eb78c31
Compare
One way to test the initial 'pickup' timeout is to simply shut down goferd on the client.
for some reason time.sleep() did not work for me, but it may have been a serverside issue at the time. |
[test] |
@iNecas does this failure strike you? http://ci.theforeman.org/job/test_katello_core/13049/testReport/ |
@ehelms it fails because https://github.com/Katello/katello/pull/5225/files#diff-3ba349775f9c0dd7cdf95b0fdc340077R19 passes '', instead of some number, that is expected: the settings needs to be set in testing environment to work properly |
@iNecas thanks, I am going to take this PR and attempt to fix the tests and will push a new PR with them if you don't mind doing the final review. I have already tested this change as is in a production environment. |
The first will fail the task if the client does not pick up the task
this likely means that either the client is not running, goferd is not running,
or goferd is having some sort of communication issue. (Default 20 seconds)
The second will fail if the client has picked up the task but has not completed it
after some time. This could happen if the link is really really slow, or the client dies
in the middle of a content action. (Default to 60 minutes)