You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
File "cartography/sync.py", line 63, in run
stage_func(neo4j_session, config)
File "intelmodules/lyft/aws.py", line 200, in lyft_start_aws_ingestion
common_job_parameters
File "cartography/intel/aws/__init__.py", line 60, in _sync_multiple_accounts
_sync_one_account(session, boto3_session, account_id, regions, sync_tag, common_job_parameters)
File "cartography/intel/aws/__init__.py", line 24, in _sync_one_account
s3.sync(session, boto3_session, account_id, sync_tag, common_job_parameters)
File "cartography/intel/aws/s3.py", line 322, in sync
load_s3_details(neo4j_session, acl_and_policy_data_iter, current_aws_account_id, aws_update_tag)
File "cartography/intel/aws/s3.py", line 132, in load_s3_details
for bucket, acl, policy in s3_details_iter:
File "cartography/intel/aws/s3.py", line 25, in get_s3_bucket_details
acl = get_acl(bucket, client)
File "cartography/intel/aws/s3.py", line 53, in get_acl
acl = client.get_bucket_acl(Bucket=bucket['Name'])
File "botocore/client.py", line 357, in _api_call
return self._make_api_call(operation_name, kwargs)
File "botocore/client.py", line 661, in _make_api_call
raise error_class(parsed_response, operation_name)
botocore.errorfactory.NoSuchBucket: An error occurred (NoSuchBucket) when calling the GetBucketAcl operation: The specified bucket does not exist
Possible race condition - the bucket might have been deleted after the call to get_s3_bucket_list but before get_s3_bucket_details. This crash is similar to #12.
Side note: it would be helpful to add information in the exception messages on which bucket caused this crash.
The text was updated successfully, but these errors were encountered:
Possible race condition - the bucket might have been deleted after the call to
get_s3_bucket_list
but beforeget_s3_bucket_details
. This crash is similar to #12.Side note: it would be helpful to add information in the exception messages on which bucket caused this crash.
The text was updated successfully, but these errors were encountered: