Currently the SDK supports a global timeout, for the complete execution of operations, but it doesn't support a timeout specific for connection establishment. This is very convenient to detect problems when using incorrect IP addresses, as otherwise the application always has to wait for the default TCP timeout. The SDK should have a new `connect_timeout` parameter in the constructor.
To verify select an IP address that can doesn't respond. The easy way is to use the "iptables" command to just make sure that the traffic to that IP address is dropped: # iptables --table filter --append OUTPUT --dest 192.168.122.100 --jump DROP Then create a script that tries to use that IP address: ---8<--- require 'logger' require 'ovirtsdk4' # Create the connection to the server: connection = OvirtSDK4::Connection.new( url: 'https://192.168.122.100/ovirt-engine/api', username: 'admin@internal', password: 'redhat123', insecure: true ) # Test the connection: connection.test(raise_exception: true) # Close the connection: connection.close ---8<--- This will fail, but it take several minutes, till the the TCP time-out expires. Repeat the same adding the new `connect_timeout` parameter, for example setting it to 10 seconds: ---8<--- require 'logger' require 'ovirtsdk4' # Create the connection to the server: connection = OvirtSDK4::Connection.new( url: 'https://192.168.122.100/ovirt-engine/api', username: 'admin@internal', password: 'redhat123', insecure: true, connect_timeout: 10 ) # Test the connection: connection.test(raise_exception: true) # Close the connection: connection.close ---8<--- It should fail anyhow, but much earlier, after 10 seconds.
Verified using method suggested by Juan, with connect_timeout parameter such request fails after given number of seconds. Used sdk version 4.2.0.beta2, RHVM 4.1.8.1.