[ 
https://issues.apache.org/jira/browse/HADOOP-19513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17938175#comment-17938175
 ] 

Steve Loughran commented on HADOOP-19513:
-----------------------------------------

Can happen with third party stores too, i think there I just ignore them
options 
* add another test.fs.s3a. switch and allow for all location tests to be 
skipped. 
* add a flag which declares they'll be rejected, and then expect failures 
(best?)

Looking at the tests, many seem to consider various exception types as valid 
outcomes. Maybe AWSUnsupportedFeatureException should be added to the list, so 
3express is automatically handled

> S3A: ITestS3AEndpointRegion fails when using with access points
> ---------------------------------------------------------------
>
>                 Key: HADOOP-19513
>                 URL: https://issues.apache.org/jira/browse/HADOOP-19513
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: fs/s3
>    Affects Versions: 3.5.0, 3.4.2
>            Reporter: Ahmar Suhail
>            Priority: Minor
>
> failures are of the form:
> {{software.amazon.awssdk.core.exception.SdkClientException: Invalid 
> configuration: region from ARN `us-east-1` does not match client region 
> `us-east-2` and UseArnRegion is `false`}}
> {{ }}
> {{at 
> software.amazon.awssdk.core.exception.SdkClientException$BuilderImpl.build(SdkClientException.java:111)}}
> {{ }}
> {{happens because when making the head request in the tests, we do }}
> {{HeadBucketRequest.builder().bucket(getFileSystem().getBucket()).build();}}
> {{ }}
> {{when using access points, bucket is 
> "arn:aws:s3:us-east-1:xxxx:accesspoint/test-bucket", so client gets the 
> region from the ARN which does not match the configured region. }}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to