Once I got a DNS error (I am running this from home, on my laptop):

---- parallel stdout ----
Error: the transport reports an error: error sending request for url (https://storage.googleapis.com/upload/storage/v1/b/coryan-test-bucket/o?uploadType=multipart&name=dc0d9e8b-b534-487a-b285-5f40ca473bcd%2Fobject-000)

Caused by:
    0: error sending request for url (https://storage.googleapis.com/upload/storage/v1/b/coryan-test-bucket/o?uploadType=multipart&name=dc0d9e8b-b534-487a-b285-5f40ca473bcd%2Fobject-000)
    1: client error (Connect)
    2: dns error
    3: failed to lookup address information: nodename nor servname provided, or not known

The retry loop can handle such errors, but requires idempotent requests, and therefore request preconditions.

I am wrong in that last bit. The DNS + connection errors are always retryable, even if the operation is not idempotent. No request data never left the local computer.

This affects both the Aip194Strict policy and the default policy for storage.

Originally posted by @coryan in #3574