Skip to content
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

SSH communicator - Reset retries counter, sleep between connection attempts #12292

Closed
wants to merge 1 commit into from

Conversation

avoidik
Copy link

@avoidik avoidik commented Apr 10, 2021

Relevant issue - #12270

Rework of #12272

@hashicorp-cla
Copy link

hashicorp-cla commented Apr 10, 2021

CLA assistant check
All committers have signed the CLA.

@soapy1
Copy link
Contributor

soapy1 commented Jan 16, 2023

Hi there,

It looks like this has been resolved within a previously shipped version of Vagrant so I am now closing this issue. If the original issue was not fully resolved, please reopen this issue or create a new one.

Cheers!

@soapy1 soapy1 closed this Jan 16, 2023
@avoidik
Copy link
Author

avoidik commented Jan 17, 2023

Hello over there,

There's still no gap between connection attempts, and SSH exceptions aren't considered as retryable in the latest version, but of course it's up to you to decide is this a bug or feature.

Cheers.

@soapy1
Copy link
Contributor

soapy1 commented Jan 17, 2023

Hey there,

There's still no gap between connection attempts

Yup, that issue is open at #10776. I think it would be nice if the solution had user configurable retry delay, similar to the winrm plugin. This is addressed in an existing PR #13047.

Thanks for the contribution!

@avoidik
Copy link
Author

avoidik commented Jan 18, 2023

Hey @soapy1

Worth noting that in the current implementation there is no retries at all due to this line, which effectively limits retries to 1.

https://github.com/hashicorp/vagrant/blob/main/plugins/communicators/ssh/communicator.rb#L87

Could you please finally decide in which PR you would like to see this fix to be applied? Thank you.

@soapy1
Copy link
Contributor

soapy1 commented Jan 18, 2023

Worth noting that in the current implementation there is no retries at all due to this line, which effectively limits retries to 1.

yup, I see you also noted this as a comment on the above mentioned PR. So, I think it's appropriate to resolve it in PR#13047. Thanks for your contribution!

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Feb 18, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants