[
https://issues.apache.org/jira/browse/HADOOP-19037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18024573#comment-18024573
]
ASF GitHub Bot commented on HADOOP-19037:
-----------------------------------------
shintaroonuma opened a new pull request, #6486:
URL: https://github.com/apache/hadoop/pull/6486
<!--
Thanks for sending a pull request!
1. If this is your first time, please read our contributor guidelines:
https://cwiki.apache.org/confluence/display/HADOOP/How+To+Contribute
2. Make sure your PR title starts with JIRA issue id, e.g.,
'HADOOP-17799. Your PR title ...'.
-->
### Description of PR
Jira: https://issues.apache.org/jira/browse/HADOOP-19037
Currently ITestS3AConfiguration.testS3SpecificSignerOverride failing when
`~/.aws/config` profile region is not set. This is because if a region is not
provided to STS client it will fall back to using the SDK
DefaultAwsRegionProviderChain: env var, profile, EC2 Metadata(IMDS) to get the
client signing region. If none of these providers are successful, this test
will fail. This PR sets this test STS client region to not rely on the SDK
region provider chain.
We will continue to have test coverage of configuring STS client builder in
ITestS3ATemporaryCredentials.
### How was this patch tested?
Tested with a bucket in eu-west-1 with `mvn clean verify -Dparallel-tests
-DtestsThreadCount=16`
- With a no region `~/.aws/config `
All tests passing other than 2 failures:
```
ITestS3ACommitterFactory.testEverything (testInvalidFileBinding())
ITestS3AConfiguration.testRequestTimeout (Expected:
https://issues.apache.org/jira/browse/HADOOP-19022)
```
### For code changes:
- [x] Does the title or this PR starts with the corresponding JIRA issue id
(e.g. 'HADOOP-17799. Your PR title ...')?
- [x] Object storage: have the integration tests been executed and the
endpoint declared according to the connector-specific documentation?
- [ ] If adding new dependencies to the code, are these dependencies
licensed in a way that is compatible for inclusion under [ASF
2.0](http://www.apache.org/legal/resolved.html#category-a)?
- [ ] If applicable, have you updated the `LICENSE`, `LICENSE-binary`,
`NOTICE-binary` files?
> S3A: S3A: ITestS3AConfiguration failing with region problems
> ------------------------------------------------------------
>
> Key: HADOOP-19037
> URL: https://issues.apache.org/jira/browse/HADOOP-19037
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3, test
> Affects Versions: 3.4.0
> Reporter: Steve Loughran
> Priority: Major
> Labels: pull-request-available
>
> After commented out the default region in my ~/.aws/config [default} profile,
> test ITestS3AConfiguration. testS3SpecificSignerOverride() fails
> {code}
> [ERROR]
> testS3SpecificSignerOverride(org.apache.hadoop.fs.s3a.ITestS3AConfiguration)
> Time elapsed: 0.054 s <<< ERROR!
> software.amazon.awssdk.core.exception.SdkClientException: Unable to load
> region from any of the providers in the chain
> software.amazon.awssdk.regions.providers.DefaultAwsRegionProviderChain@12c626f8:
>
> [software.amazon.awssdk.regions.providers.SystemSettingsRegionProvider@ae63559:
> Unable to load region from system settings. Region must be specified either
> via environment variable (AWS_REGION) or system property (aws.region).,
> software.amazon.awssdk.regions.providers.AwsProfileRegionProvider@6e6cfd4c:
> No region provided in profile: default,
> software.amazon.awssdk.regions.providers.InstanceProfileRegionProvider@139147de:
> EC2 Metadata is disabled. Unable to retrieve region information from EC2
> Metadata service.]
> {code}
> I'm worried the sdk update has rolled back to the 3.3.x region problems where
> well-configured developer setups / ec2 deployments hid problems. certainly we
> can see the code is checking these paths
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
