You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Xiao Chen (JIRA)" <ji...@apache.org> on 2016/02/01 20:28:39 UTC
[jira] [Updated] (HADOOP-12699) TestKMS#testKMSProvider
intermittently fails during 'test rollover draining'
[ https://issues.apache.org/jira/browse/HADOOP-12699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Xiao Chen updated HADOOP-12699:
-------------------------------
Attachment: HADOOP-12699.08.patch
Had offline discussion with [~asuresh], [~andrew.wang] and [~zhz]. The conclusion is that the scenario is not supported, and we should just fix the unittest to make sure new key is generated after draining the queue. We should also update docs about this behavior due to caching, to set user expectation.
Patch 08 fixes the unit tests.
I didn't find a good place to explicitly document this, so just put it on the javadoc. Please advice if there's a better place I overlooked.
Thanks all for the discussions and reviews.
> TestKMS#testKMSProvider intermittently fails during 'test rollover draining'
> ----------------------------------------------------------------------------
>
> Key: HADOOP-12699
> URL: https://issues.apache.org/jira/browse/HADOOP-12699
> Project: Hadoop Common
> Issue Type: Bug
> Reporter: Xiao Chen
> Assignee: Xiao Chen
> Attachments: HADOOP-12699.01.patch, HADOOP-12699.02.patch, HADOOP-12699.03.patch, HADOOP-12699.04.patch, HADOOP-12699.06.patch, HADOOP-12699.07.patch, HADOOP-12699.08.patch, HADOOP-12699.repro.2, HADOOP-12699.repro.patch
>
>
> I've seen several failures of testKMSProvider, all failed in the following snippet:
> {code}
> // test rollover draining
> KeyProviderCryptoExtension kpce = KeyProviderCryptoExtension.
> createKeyProviderCryptoExtension(kp);
> .....
> EncryptedKeyVersion ekv1 = kpce.generateEncryptedKey("k6");
> kpce.rollNewVersion("k6");
> EncryptedKeyVersion ekv2 = kpce.generateEncryptedKey("k6");
> Assert.assertNotEquals(ekv1.getEncryptionKeyVersionName(),
> ekv2.getEncryptionKeyVersionName());
> {code}
> with error message
> {quote}Values should be different. Actual: k6@0{quote}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)