#1994 closed defect (somebody else's problem)

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

Reported by: Zancas Owned by: Zancas
Priority: normal Milestone: undecided
Component: code-storage Version: 1.10.0
Keywords: cloud S3 Cc:
Launchpad Bug:

Description

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.

Change History (7)

comment:1 Changed at 2013-05-30T19:07:46Z by 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.)

Last edited at 2013-05-30T19:08:57Z by daira (previous) (diff)

comment:2 follow-up: Changed at 2013-05-30T19:13:26Z by 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.)

comment:3 in reply to: ↑ 2 ; follow-up: Changed at 2013-06-06T15:58:25Z by 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?

comment:4 in reply to: ↑ 3 Changed at 2013-06-14T23:36:26Z by daira

[deleted; comment was based on an error]

Last edited at 2013-06-14T23:38:16Z by daira (previous) (diff)

comment:5 follow-up: Changed at 2013-06-21T03:14:59Z by Zancas

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

comment:6 in reply to: ↑ 5 Changed at 2013-06-21T09:26:58Z by 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.

comment:7 Changed at 2013-07-02T22:31:12Z by daira

  • Resolution set to somebody else's problem
  • Status changed from new to closed
Note: See TracTickets for help on using tickets.