[
https://issues.apache.org/jira/browse/HADOOP-19027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18023592#comment-18023592
]
ASF GitHub Bot commented on HADOOP-19027:
-----------------------------------------
steveloughran commented on PR #8003:
URL: https://github.com/apache/hadoop/pull/8003#issuecomment-3348230998
S3 London. All good with updated tests.
Failure in `ITestAssumeRole` which seems unrelated (will need to test on
base branch-3.3)
{code}
[ERROR]
ITestAssumeRole.testAssumeRoleBadInnerAuth:263->expectFileSystemCreateFailure:137
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:
com.amazonaws.services.securitytoken.model.AWSSecurityTokenServiceException:
Invalid key=value pair (missing equal-sign) in Authorization header (hashed
with SHA-256 and encoded with Base64):
'hvHJSzfhtkBgtrEOkT9w/UT3So5LWUnDLLsTKYln5vE='. (Service:
AWSSecurityTokenService; Status Code: 400; Error Code: IncompleteSignature;
Request ID: 4f76f95a-3933-4312-858b-3f1d123bf14f; Proxy:
null):IncompleteSignature: Invalid key=value pair (missing equal-sign) in
Authorization header (hashed with SHA-256 and encoded with Base64):
'hvHJSzfhtkBgtrEOkT9w/UT3So5LWUnDLLsTKYln5vE='. (Service:
AWSSecurityTokenService; Status Code: 400; Error Code: IncompleteSignature;
Request ID: 4f76f95a-3933-4312-858b-3f1d123bf14f; Proxy: null)
{code}
> S3A: S3AInputStream doesn't recover from HTTP/channel exceptions
> ----------------------------------------------------------------
>
> Key: HADOOP-19027
> URL: https://issues.apache.org/jira/browse/HADOOP-19027
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
> Affects Versions: 3.4.0
> Reporter: Steve Loughran
> Assignee: Steve Loughran
> Priority: Major
> Labels: pull-request-available
> Fix For: 3.4.0, 3.5.0, 3.4.1
>
>
> S3AInputStream doesn't seem to recover from Http exceptions raised through
> HttpClient or through OpenSSL.
> * review the recovery code to make sure it is retrying enough, it looks
> suspiciously like it doesn't
> * detect the relevant openssl, shaded httpclient and unshaded httpclient
> exceptions, map to a standard one and treat as comms error in our retry policy
> This is not the same as the load balancer/proxy returning 443/444 which we
> map to AWSNoResponseException. We can't reuse that as it expects to be
> created from an
> {{software.amazon.awssdk.awscore.exception.AwsServiceException}} exception
> with the relevant fields...changing it could potentially be incompatible.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
