Return-Path: Delivered-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org Received: (qmail 31789 invoked from network); 14 Apr 2011 16:23:50 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 14 Apr 2011 16:23:50 -0000 Received: (qmail 68442 invoked by uid 500); 14 Apr 2011 16:23:47 -0000 Delivered-To: apmail-hadoop-hdfs-issues-archive@hadoop.apache.org Received: (qmail 68408 invoked by uid 500); 14 Apr 2011 16:23:47 -0000 Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hdfs-issues@hadoop.apache.org Delivered-To: mailing list hdfs-issues@hadoop.apache.org Received: (qmail 68374 invoked by uid 99); 14 Apr 2011 16:23:47 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 14 Apr 2011 16:23:47 +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; Thu, 14 Apr 2011 16:23:44 +0000 Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116]) by hel.zones.apache.org (Postfix) with ESMTP id 61C64A1D27 for ; Thu, 14 Apr 2011 16:23:06 +0000 (UTC) Date: Thu, 14 Apr 2011 16:23:06 +0000 (UTC) From: "Hadoop QA (JIRA)" To: hdfs-issues@hadoop.apache.org Message-ID: <1161828519.58024.1302798186397.JavaMail.tomcat@hel.zones.apache.org> In-Reply-To: <16309532.44060.1302279726839.JavaMail.tomcat@hel.zones.apache.org> Subject: [jira] [Commented] (HDFS-1821) FileContext.createSymlink with kerberos enabled sets wrong owner MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/HDFS-1821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13019893#comment-13019893 ] Hadoop QA commented on HDFS-1821: --------------------------------- -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12476347/HDFS-1821-2.patch against trunk revision 1091874. +1 @author. The patch does not contain any @author tags. +1 tests included. The patch appears to include 3 new or modified tests. +1 javadoc. The javadoc tool did not generate any warning messages. +1 javac. The applied patch does not increase the total number of javac compiler warnings. +1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9) warnings. +1 release audit. The applied patch does not increase the total number of release audit warnings. -1 core tests. The patch failed these core unit tests: org.apache.hadoop.hdfs.server.datanode.TestBlockReport org.apache.hadoop.hdfs.TestFileConcurrentReader -1 contrib tests. The patch failed contrib unit tests. +1 system test framework. The patch passed system test framework compile. Test results: https://hudson.apache.org/hudson/job/PreCommit-HDFS-Build/367//testReport/ Findbugs warnings: https://hudson.apache.org/hudson/job/PreCommit-HDFS-Build/367//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html Console output: https://hudson.apache.org/hudson/job/PreCommit-HDFS-Build/367//console This message is automatically generated. > FileContext.createSymlink with kerberos enabled sets wrong owner > ---------------------------------------------------------------- > > Key: HDFS-1821 > URL: https://issues.apache.org/jira/browse/HDFS-1821 > Project: Hadoop HDFS > Issue Type: Bug > Affects Versions: 0.22.0 > Environment: Kerberos enabled on cluster > Reporter: John George > Assignee: John George > Attachments: HDFS-1821-2.patch, HDFS-1821.patch > > > TEST SETUP > Using attached sample hdfs java program that illustrates the issue. > Using cluster with Kerberos enabled on cluster > # Compile instructions > $ javac Symlink.java -cp `hadoop classpath` > $ jar -cfe Symlink.jar Symlink Symlink.class > # create test file for symlink to use > 1. hadoop fs -touchz /user/username/filetest > # Create symlink using file context > 2. hadoop jar Symlink.jar ln /user/username/filetest /user/username/testsymlink > # Verify owner of test file > 3. hadoop jar Symlink.jar ls /user/username/ > -rw-r--r-- username hdfs /user/jeagles/filetest > -rwxrwxrwx username@XX.XXXX.XXXXX.XXX hdfs /user/username/testsymlink > RESULTS > 1. Owner shows 'username@XX.XXXX.XXXXX.XXX' for symlink, expecting 'username'. > 2. Symlink is corrupted and can't removed, since it was created with an invalid user > ------------------------ > Sample program to create Symlink > FileContext fc = FileContext.getFileContext(getConf()); > fc.createSymlink(target, symlink, false); > --------------------------------------- -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira