S3 Error during initialization of S3 store to use with S3(cloud) backend

[Zancas]

I attempted to create an S3 bucket to use with the S3 backend (by signing up for the LeastAuthority cyphertext storage service). Here's a normal message printed during such a signup:

Creating S3 bucket in 'US East' region...

it was immediately followed by this error:

Failure notification sent for the following error: S3Error: Error Message: A conflicting conditional operation is currently in progress against this resource. Please try again. Command failed with exit code 1.

[daira]

Here's the traceback and the full message from S3 (from signup_logs/2013-05-30T163714Z-bwsr6f7llsqkyj7o2qoade3enfjeh2es on phi):

[Failure instance: Traceback: <class 'txaws.s3.exception.S3Error'>: Error Message: A conflicting conditional operation is currently in progress against this resource. Please try again.
/usr/local/lib/python2.7/dist-packages/Twisted-12.3.0-py2.7-linux-i686.egg/twisted/protocols/policies.py:125:connectionLost
/usr/local/lib/python2.7/dist-packages/Twisted-12.3.0-py2.7-linux-i686.egg/twisted/web/client.py:207:connectionLost
/usr/local/lib/python2.7/dist-packages/Twisted-12.3.0-py2.7-linux-i686.egg/twisted/internet/defer.py:381:callback
/usr/local/lib/python2.7/dist-packages/Twisted-12.3.0-py2.7-linux-i686.egg/twisted/internet/defer.py:489:_startRunCallbacks
--- <exception caught here> ---
/usr/local/lib/python2.7/dist-packages/Twisted-12.3.0-py2.7-linux-i686.egg/twisted/internet/defer.py:576:_runCallbacks
/usr/local/lib/python2.7/dist-packages/txAWS-0.2.1.post4-py2.7.egg/txaws/s3/client.py:31:s3_error_wrapper
/usr/local/lib/python2.7/dist-packages/txAWS-0.2.1.post4-py2.7.egg/txaws/client/base.py:46:error_wrapper
]
<?xml version="1.0" encoding="UTF-8"?>
<Error><Code>OperationAborted</Code><Message>A conflicting conditional operation is currently in progress against this resource. Please try again.</Message><RequestId>8F13F4602048877D</RequestId><HostId>LInprCG2ZTA8kNhBvIiXZavgoGzDBkgHxvjZWy8fSqgOMr2yvDCrBNPX0jijG/bz</HostId></Error>
>S3Error: Error Message: A conflicting conditional operation is currently in progress against this resource. Please try again.>

(That doesn't actually tell us anything new, just added for completeness.)

[daira]

I was actually hoping to get the HTTP error code from the log, but txaws exception messages don't include that. (The error handling in Tahoe-LAFS' S3 code does include it.)

[Zancas]

Replying to daira:

I was actually hoping to get the HTTP error code from the log, but txaws exception messages don't include that. (The error handling in Tahoe-LAFS' S3 code does include it.)

Should we put adding HTTP error codes to txaws exceptions into a scrumdo story?

[daira]

Replying to Zancas:

Replying to daira:

I was actually hoping to get the HTTP error code from the log, but txaws exception messages don't include that. (The error handling in Tahoe-LAFS' S3 code does include it.)

Should we put adding HTTP error codes to txaws exceptions into a scrumdo story?

I'd rather eliminate Tahoe-LAFS' dependency on txaws. All of the container implementations for other services are making direct HTTP requests, and S3Container could do the same without a significant increase in code size or complexity (given that we're having to override the HMAC signature computation anyway).

[Zancas]

Should we storify (on ScrumDo) eliminating our dependence on txaws?

[daira]

Replying to Zancas:

Should we storify (on ScrumDo) eliminating our dependence on txaws?

I only want to do that for Tahoe-LAFS itself (which should be a Tahoe-LAFS ticket), but that isn't relevant to this error from the LeastAuthority automation.

[daira]

Moved to ​#3 on LeastAuthority.com's github tracker.