You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-dev@hadoop.apache.org by "Steve Loughran (Jira)" <ji...@apache.org> on 2019/10/15 12:54:00 UTC

[jira] [Resolved] (HADOOP-16634) S3A ITest failures without S3Guard

     [ https://issues.apache.org/jira/browse/HADOOP-16634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Steve Loughran resolved HADOOP-16634.
-------------------------------------
    Fix Version/s: 3.3.0
       Resolution: Fixed

fixed while debugging HADOOP-16635

> S3A ITest failures without S3Guard
> ----------------------------------
>
>                 Key: HADOOP-16634
>                 URL: https://issues.apache.org/jira/browse/HADOOP-16634
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: fs/s3, test
>    Affects Versions: 3.3.0
>            Reporter: Steve Loughran
>            Assignee: Steve Loughran
>            Priority: Major
>             Fix For: 3.3.0
>
>
> This has probably been lurking for a while but we hadn't noticed because if your auth-keys xml settings mark a specific store as guarded, then the maven CLI settings aren't picked up. Remove those bindings and things fail.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-dev-help@hadoop.apache.org