Return-Path: 
 <hdfs-issues-return-39802-apmail-hadoop-hdfs-issues-archive=hadoop.apache.org@hadoop.apache.org>
X-Original-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org
Delivered-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 81768CCB3
	for <apmail-hadoop-hdfs-issues-archive@minotaur.apache.org>;
 Wed, 25 Apr 2012 13:34:42 +0000 (UTC)
Received: (qmail 90470 invoked by uid 500); 25 Apr 2012 13:34:42 -0000
Delivered-To: apmail-hadoop-hdfs-issues-archive@hadoop.apache.org
Received: (qmail 90419 invoked by uid 500); 25 Apr 2012 13:34:42 -0000
Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:hdfs-issues-help@hadoop.apache.org>
List-Unsubscribe: <mailto:hdfs-issues-unsubscribe@hadoop.apache.org>
List-Post: <mailto:hdfs-issues@hadoop.apache.org>
List-Id: <hdfs-issues.hadoop.apache.org>
Reply-To: hdfs-issues@hadoop.apache.org
Delivered-To: mailing list hdfs-issues@hadoop.apache.org
Received: (qmail 90411 invoked by uid 99); 25 Apr 2012 13:34:42 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 25 Apr 2012 13:34:42 +0000
X-ASF-Spam-Status: No, hits=-2000.0 required=5.0
	tests=ALL_TRUSTED,T_RP_MATCHES_RCVD
X-Spam-Check-By: apache.org
Received: from [140.211.11.116] (HELO hel.zones.apache.org) (140.211.11.116)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 25 Apr 2012 13:34:39 +0000
Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116])
	by hel.zones.apache.org (Postfix) with ESMTP id AC51C40C06B
	for <hdfs-issues@hadoop.apache.org>; Wed, 25 Apr 2012 13:34:18 +0000 (UTC)
Date: Wed, 25 Apr 2012 13:34:18 +0000 (UTC)
From: "Daryn Sharp (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <827497.259.1335360858720.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1001064934.9938.1335279818178.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (HDFS-3317) Balancer error text changed again,
 not sending Auth, is this expected?
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394


    [ 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