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

No setting for command timeout #282

Open
jkugler opened this issue Apr 22, 2019 · 0 comments
Open

No setting for command timeout #282

jkugler opened this issue Apr 22, 2019 · 0 comments

Comments

@jkugler
Copy link

jkugler commented Apr 22, 2019

We have a misbehaving ESXi server that will complete TLS negotiation, but then the API itself hangs (the client just sits there waiting for a response), so it doesn't have a "connect timeout," but we get this:

-----> Creating <source-ubuntu-1204-bento>...
>>>>>> ------Exception-------
>>>>>> Class: Kitchen::ActionFailed
>>>>>> Message: 1 actions failed.
>>>>>>     Failed to complete #create action: [Command timed out after 60000s:
Command exceeded allowed execution time, process terminated

We don't need 16+ hours to know something is wrong. :)

A setting of "command timeout" or similar would be nice so we could set it to something like five or 10 minutes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant