Reduce the default oVirt open timeout to 1 minute #15099
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.
Currently the timeout used when opening connections to oVirt isn't
explicitly set. That means that when trying to connect to an oVirt
system that doesn't exist, or that doesn't respond, it may take as long
as the TCP timeout till the error is detected. In a typical setup on top
of Linux this timeout is approx 2 minutes and 8 seconds. But in
production environments the web server that is in front of the ManageIQ
user interface has a request timeout explicitly set to 2 minutes. This
means that validation of credentials for oVirt systems that don't exist,
or don't respond are ignored by the ManageIQ user interface, because it
gives up before the error is detected by the ManageIQ server. To avoid
that issue this patch changes the default connection timeout used by the
oVirt provider to 1 minute.
https://bugzilla.redhat.com/1448065