[
https://issues.apache.org/jira/browse/HADOOP-11117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14144596#comment-14144596
]
Steve Loughran commented on HADOOP-11117:
-----------------------------------------
I agree ... but this is something minimal which can go in with little/no work
—though it looks like a couple of tests are not picking up the changed text.
What we could do long term is replicate some of the stuff we did for the
networking errors: point to wiki pages. But how is anyone going to make sense
of a {{NoMatchException}} ? I don't want to write the wiki page for that.
> UGI HadoopLoginModule doesn't catch & wrap all kerberos-related exceptions
> --------------------------------------------------------------------------
>
> Key: HADOOP-11117
> URL: https://issues.apache.org/jira/browse/HADOOP-11117
> Project: Hadoop Common
> Issue Type: Bug
> Components: security
> Affects Versions: 2.5.1
> Reporter: Steve Loughran
> Assignee: Steve Loughran
> Priority: Minor
> Fix For: 2.6.0
>
> Attachments: HADOOP-11117-001.patch
>
>
> If something is failing with kerberos login,
> {{UserGroupInformation.loginUserFromKeytabAndReturnUGI()}} should fail with
> useful information. But not all exceptions from the inner code are caught and
> converted to LoginException. Those exceptions that aren't wrapped have their
> text and stack trace lost somewhere in the javax code, leaving on the text
> "login failed" and a stack trace of no value whatsoever.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
