[ https://issues.apache.org/jira/browse/HADOOP-10842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14066116#comment-14066116 ]
Hadoop QA commented on HADOOP-10842: ------------------------------------ {color:red}-1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12656461/HADOOP-10842.2.patch against trunk revision . {color:green}+1 @author{color}. The patch does not contain any @author tags. {color:green}+1 tests included{color}. The patch appears to include 1 new or modified test files. {color:green}+1 javac{color}. The applied patch does not increase the total number of javac compiler warnings. {color:green}+1 javadoc{color}. There were no new javadoc warning messages. {color:green}+1 eclipse:eclipse{color}. The patch built with eclipse:eclipse. {color:green}+1 findbugs{color}. The patch does not introduce any new Findbugs (version 2.0.3) warnings. {color:green}+1 release audit{color}. The applied patch does not increase the total number of release audit warnings. {color:red}-1 core tests{color}. The patch failed these unit tests in hadoop-common-project/hadoop-common: org.apache.hadoop.ipc.TestIPC org.apache.hadoop.fs.TestSymlinkLocalFSFileSystem org.apache.hadoop.fs.TestSymlinkLocalFSFileContext {color:green}+1 contrib tests{color}. The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-HADOOP-Build/4312//testReport/ Console output: https://builds.apache.org/job/PreCommit-HADOOP-Build/4312//console This message is automatically generated. > CryptoExtension generateEncryptedKey method should receive the key name > ----------------------------------------------------------------------- > > Key: HADOOP-10842 > URL: https://issues.apache.org/jira/browse/HADOOP-10842 > Project: Hadoop Common > Issue Type: Bug > Components: security > Affects Versions: 3.0.0 > Reporter: Alejandro Abdelnur > Assignee: Arun Suresh > Fix For: 3.0.0 > > Attachments: HADOOP-10842-10841-COMBO.1.patch, HADOOP-10842.1.patch, > HADOOP-10842.2.patch > > > Generating an EEK should be done using always the current keyversion of a key > name. We should enforce that by API by handing off EEKs for the last > keyversion of a keyname only, thus we should ask for EEKs for a keyname and > the {{CryptoExtension}} should use the last keyversion. -- This message was sent by Atlassian JIRA (v6.2#6252)