[
https://issues.apache.org/jira/browse/HADOOP-13540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15477890#comment-15477890
]
Hudson commented on HADOOP-13540:
---------------------------------
SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #10419 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/10419/])
HADOOP-13540 improve section on troubleshooting s3a auth problems. (stevel: rev
4b6d795f28591df7761186bc5c8d31dcd1a5a99d)
* (edit) hadoop-tools/hadoop-aws/src/site/markdown/tools/hadoop-aws/index.md
> improve section on troubleshooting s3a auth problems
> ----------------------------------------------------
>
> Key: HADOOP-13540
> URL: https://issues.apache.org/jira/browse/HADOOP-13540
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: documentation, fs/s3
> Affects Versions: 2.8.0
> Reporter: Steve Loughran
> Assignee: Steve Loughran
> Priority: Minor
> Fix For: 2.8.0
>
> Attachments: HADOOP-13540-001.patch, HADOOP-13540-branch-2-002.patch,
> HADOOP-13540-branch-2-003.patch, HADOOP-13540-branch-2-004.patch
>
>
> We should add more on how to go about diagnosing s3a auth problems.
> When it happens, the need to keep the credentials secret makes it hard to
> automate diagnostics; we can at least provide a better runbook for users
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
