winrm connection timeout, perhaps #25350
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
2 commits here:
github.com/masterzen/winrm
andgithub.com/packer-community/winrmcp
libraries to lates. These did not make a different to the issue I was troubleshooting, but it also did no harm so I thought it worth upgrading. No harm in rolling this commit back if there are any concerns.winrm.Endpoint
. This timeout is used in the underlying tcp connection: (winrm documentation)This is not a solution to #22006 - I am still working on a reproduction that succeeds in one version of terraform and hangs in another - but I think this is a solid first step: actual timeout errors as opposed to hanging.
As a side note/additional information: The configured timeout (in both packer and terraform) is used in the
winrm.NewClientWithParameters
. Packer does not set thewinrm.Endpoint
timeout (defaults to 60s).