hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daryn Sharp (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-3317) Balancer error text changed again, not sending Auth, is this expected?
Date Wed, 25 Apr 2012 13:34:18 GMT

    [ https://issues.apache.org/jira/browse/HDFS-3317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13261634#comment-13261634
] 

Daryn Sharp commented on HDFS-3317:
-----------------------------------

I'd like to see {{toString()}} reverted to include the authentication information.  It has
proved to be very valuable in debugging security & token related issues.
                
> Balancer error text changed again, not sending Auth, is this expected?
> ----------------------------------------------------------------------
>
>                 Key: HDFS-3317
>                 URL: https://issues.apache.org/jira/browse/HDFS-3317
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: balancer
>    Affects Versions: 1.0.2
>         Environment: QE
>            Reporter: patrick white
>            Priority: Minor
>
> We have a negative test case for Balancer which looks for a report of a not-authorized
user attempting to run Balancer. This recently failed because the return string changed, the
authentication "(auth:KERBEROS)" is no longer sent. The same case failed last December because
this auth substr was added, in 205. The previous string looks like this:
> 'Received an IO exception: User <USER> (auth:KERBEROS) is not authorized for protocol
interface'
> And now looks like this:
> 'Received an IO exception: User <USER> is not authorized for protocol interface'
> While a trivial matter for the product, this fails our test automation, requiring a follow
up to confirm the change is actually expected, update the tests, so forth. This makes the
change non-trivial for validation and test maintenance purposes, so it would be very good
to have a definitive understanding of what to expect going forward.
> Do we expect additional changes here?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message