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.
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:
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.