-
Notifications
You must be signed in to change notification settings - Fork 54
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
"Sync Repository | Wait for finish the repository sync" throws "Timeout exceeded" #393
Comments
I want to make sure we are on the same page, have you set the following variables, and the async dies after the 1000 seconds times out? and if you have a LONG list of repos you may need to increase the request timeout as well, I am for adding that as a variable, just want to make sure that is indeed the problem. |
Hi Sean, I am not 100% sure that is the problem, but based on the ansible doc (https://docs.ansible.com/ansible/latest/playbook_guide/playbooks_async.html#run-tasks-concurrently-poll-0) it seems to be. From that paragraph my understanding is that when poll is 0, the timeout happens when the task runs for more that async value. This is our config:
Our AAP job fails on attempt 99
So after 99*10 seconds.. The AH Based on all this, I suspect that hardcodded 1000 in https://github.com/ansible/galaxy_collection/blob/devel/roles/collection_repository_sync/tasks/main.yml#L19 |
At first glance I think the solution here would be to set the async to be equal to |
Just in case |
Summary
"Sync Repository | Wait for finish the repository sync" throws "Timeout exceeded" after about 16 minutes (1000 seconds).
The async values should be increased or made configurable?
https://github.com/ansible/galaxy_collection/blob/devel/roles/collection_repository_sync/tasks/main.yml#L19
16 minutes seems like a small amount of time for syncing the remote repos. We have a scheduled job running it every 3 days, and sometimes the community one takes 30-40 minutes to complete.
Thank you.
Issue Type
The text was updated successfully, but these errors were encountered: