be more explicit about connection errors
urllib/requests ConnectionError is a translation of SocketError. However, when we translate this *yet again* we drop the message from Requests. That message contains the actual SocketError details, which are often critical for debugging an issue. This keeps those details in the error message as we carry this up. Change-Id: I6b753fddaebdcbcfe62680585a5b6febf62647b3
This commit is contained in:
parent
e1bf1f0e83
commit
7d26de17f5
@ -631,8 +631,14 @@ class Session(object):
|
||||
except requests.exceptions.Timeout:
|
||||
msg = 'Request to %s timed out' % url
|
||||
raise exceptions.ConnectTimeout(msg)
|
||||
except requests.exceptions.ConnectionError:
|
||||
msg = 'Unable to establish connection to %s' % url
|
||||
except requests.exceptions.ConnectionError as e:
|
||||
# NOTE(sdague): urllib3/requests connection error is a
|
||||
# translation of SocketError. However, SocketError
|
||||
# happens for many different reasons, and that low
|
||||
# level message is often really important in figuring
|
||||
# out the difference between network misconfigurations
|
||||
# and firewall blocking.
|
||||
msg = 'Unable to establish connection to %s: %s' % (url, e)
|
||||
raise exceptions.ConnectFailure(msg)
|
||||
except requests.exceptions.RequestException as e:
|
||||
msg = 'Unexpected exception for %(url)s: %(error)s' % {
|
||||
|
Loading…
Reference in New Issue
Block a user