[HDFS-13482] Crypto command should give proper exception when user is trying to create an EZ with the same key with which it is already created

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 2.8.3
• Component/s: hdfs, kms
• Assignee: Unassigned
• Reporter: Harshakiran Reddy
• Created: 19/Apr/18 12:52
• Updated: 20/Apr/18 04:05
• Resolved: 20/Apr/18 04:05

Description

Scenario:

1. Create a Dir
2. Create EZ for the above dir with Key1
3. Again you can try to create ZONE for same directory with the same Key1

hadoopclient> hadoop key list
Listing keys for KeyProvider: org.apache.hadoop.crypto.key.kms.LoadBalancingKMSClientProvider@152aa092
key2
key1
hadoopclient> hdfs dfs -mkdir /kms
hadoopclient> hdfs crypto -createZone -keyName key1 -path /kms
Added encryption zone /kms
hadoopclient> hdfs crypto -createZone -keyName key1 -path /kms
RemoteException: Attempt to create an encryption zone for a non-empty directory.

Actual Output:
===========
Exception should be like EZ is already created with the same key

Expected Output:
=============
RemoteException:Attempt to create an encryption zone for non-empty directory

Issue Links

• is duplicated by: HDFS-13483 Crypto command should give proper exception when user is trying to create an EZ with the same key with which it is already created