[
https://issues.apache.org/jira/browse/HADOOP-19257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Loughran resolved HADOOP-19257.
-------------------------------------
Fix Version/s: 3.5.0
3.4.1
Resolution: Fixed
> S3A: ITestAssumeRole.testAssumeRoleBadInnerAuth failure
> -------------------------------------------------------
>
> Key: HADOOP-19257
> URL: https://issues.apache.org/jira/browse/HADOOP-19257
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3, test
> Affects Versions: 3.4.0, 3.4.1
> Reporter: Steve Loughran
> Priority: Minor
> Labels: pull-request-available
> Fix For: 3.5.0, 3.4.1
>
>
> Not sure when this changed, but I've only just noticed today while setting up
> a new test config.
> The test {{testAssumeRoleBadInnerAuth}} is failing because the error string
> coming back from STS is slightly different.
> {code}
> [ERROR]
> testAssumeRoleBadInnerAuth(org.apache.hadoop.fs.s3a.auth.ITestAssumeRole)
> Time elapsed: 4.182 s <<< FAILURE!
> java.lang.AssertionError:
> Expected to find 'not a valid key=value pair (missing equal-sign) in
> Authorization header' but got unexpected exception:
> org.apache.hadoop.fs.s3a.AWSBadRequestException: Instantiate
> org.apache.hadoop.fs.s3a.auth.AssumedRoleCredentialProvider on /:
> software.amazon.awssdk.services.sts.model.StsException: Invalid key=value
> pair (missing equal-sign)
> {code}
> Rather than change the string to look for, lets just remove the string so it
> it less brittle in future
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
