Comment 3 for bug 1634452

Ravi, in that case this is a bug against the glanceclient, which is a separate project. That said, I'm not convinced we need to fix this. Here's why:

1. By not checking for the arguments, we can then issue a proper error if there is no image. Meaning that not stopping early, a user will see if they can actually download that image.

2. While not common on small clouds, connection errors like this are almost certainly fairly common in very large environments, especially with unreliable internet connections for clients.

Are you concerned by this connection error appearing in your logs? Or is there some other reason you think this needs fixing?