[
https://issues.apache.org/jira/browse/HADOOP-11110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14151848#comment-14151848
]
Hadoop QA commented on HADOOP-11110:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12671797/HADOOP-11110.2.patch
against trunk revision cf4631d.
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 3 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.crypto.random.TestOsSecureRandom
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-HADOOP-Build/4826//testReport/
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/4826//console
This message is automatically generated.
> JavaKeystoreProvider should not report a key as created if it was not flushed
> to the backing file
> -------------------------------------------------------------------------------------------------
>
> Key: HADOOP-11110
> URL: https://issues.apache.org/jira/browse/HADOOP-11110
> Project: Hadoop Common
> Issue Type: Bug
> Affects Versions: 2.5.0
> Reporter: Andrew Wang
> Assignee: Arun Suresh
> Attachments: HADOOP-11110.1.patch, HADOOP-11110.2.patch
>
>
> Testing with the KMS backed by JKS reveals the following:
> {noformat}
> [root@dlo-4 ~]# hadoop key create testkey -provider
> kms://http@localhost:16000/kms
> testkey has not been created. Mkdirs failed to create file:xxxxx
> ....<stack trace>....
> [root@dlo-4 ~]# hadoop key list -provider kms://http@localhost:16000/kms
> Listing keys for KeyProvider:
> KMSClientProvider[http://localhost:16000/kms/v1/]
> testkey
> {noformat}
> The JKS still has the key in memory and serves it up, but will disappear if
> the KMS is restarted since it's not flushed to the file.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
