Steve Loughran created HADOOP-19037:
---------------------------------------
Summary: 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
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: common-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-dev-h...@hadoop.apache.org
