[
https://issues.apache.org/jira/browse/HADOOP-12509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14975065#comment-14975065
]
Daniel Templeton commented on HADOOP-12509:
-------------------------------------------
Thanks for the test output. I really see no reason for this test to have
failed.
On your patch, I would recommend adding:
{code}
Assert.assertTrue("KeyProvider was created with existing keys",
kp.getKeys().isEmpty());
{code}
after the KP creation.
Also, it seems kinda wrong to fix just one of the tests. I've started a round
of cleanup on the whole of TestKMS. Seems like we should file a separate JIRA
to clean up the tests, and leave this one for actually fixing the issue, should
we ever track it down.
> org.apache.hadoop.crypto.key.kms.server.TestKMS.testKeyACLs failing
> -------------------------------------------------------------------
>
> Key: HADOOP-12509
> URL: https://issues.apache.org/jira/browse/HADOOP-12509
> Project: Hadoop Common
> Issue Type: Bug
> Components: kms, test
> Affects Versions: 3.0.0
> Environment: ASF Jenkins
> Reporter: Steve Loughran
> Assignee: Steve Loughran
> Attachments: HADOOP-12509-001.patch, Hadoop-common-trunk-Java8 #594
> test - testKeyACLs [Jenkins].pdf
>
>
> Failure of Jenkins in trunk, test
> {{org.apache.hadoop.crypto.key.kms.server.TestKMS.testKeyACLs}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
