hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mingliang Liu (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HADOOP-14129) ITestS3ACredentialsInURL sometimes fails
Date Thu, 02 Mar 2017 23:34:45 GMT

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

Mingliang Liu updated HADOOP-14129:
    Attachment: HADOOP-14129-HADOOP-13345.005.patch

@Steve I think the configuration are isolated in each test case, but the sysprop is not. So
the v5 patch will simply assume (read conf/sysprop instead of write) testing S3Guard is not
enabled. I tested this (I was able to reproduce this test failure consistently now):
# {{-Ds3guard -Ddynamo}} from mvn command line
# set config {{fs.s3a.metadatastore.impl}} in configuration file {{hadoop-tools/hadoop-aws/src/test/resources/auth-keys.xml}};
*w and w/o* -Ds3guard from mvn command line
# set per bucket config {{fs.s3a.bucket.mliu-s3guard.metadatastore.impl}} in configuration
file {{hadoop-tools/hadoop-aws/src/test/resources/auth-keys.xml}}; *w and w/o* -Ds3guard from
mvn command line

They 5 cases all passed with v5 patch.

> ITestS3ACredentialsInURL sometimes fails
> ----------------------------------------
>                 Key: HADOOP-14129
>                 URL: https://issues.apache.org/jira/browse/HADOOP-14129
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: fs/s3
>    Affects Versions: HADOOP-13345
>            Reporter: Sean Mackrory
>            Assignee: Sean Mackrory
>             Fix For: HADOOP-13345
>         Attachments: HADOOP-14129-HADOOP-13345.001.patch, HADOOP-14129-HADOOP-13345.002.patch,
HADOOP-14129-HADOOP-13345.003.patch, HADOOP-14129-HADOOP-13345.004.patch, HADOOP-14129-HADOOP-13345.005.patch
> This test sometimes fails. I believe it's expected that DynamoDB doesn't have access
to the credentials if they're embedded in the URL instead of the configuration (and IMO that's
fine - since the functionality hasn't been in previous releases and since we want to discourage
this practice especially now that there are better alternatives). Weirdly, I only sometimes
get this failure on the HADOOP-13345 branch. But if the problem turns out to be what I think
it is, a simple Assume should fix it.

This message was sent by Atlassian JIRA

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

View raw message