[HDFS-13292] Crypto command should give proper exception when trying to set key on existing EZ directory

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.8.3
• Fix Version/s: 3.2.0
• Component/s: hdfs, kms
• Assignee: Ranith Sardar
• Reporter: Harshakiran Reddy
• Created: 15/Mar/18 10:25
• Updated: 27/Apr/18 09:05
• Resolved: 07/Apr/18 06:06

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 Diff Key i.e Key2

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 dfs -put bigdata_env /kms/file1
hadoopclient> hdfs crypto -createZone -keyName key1 -path /kms
RemoteException: Attempt to create an encryption zone for a non-empty directory.
hadoopclient> hdfs dfs -rmr /kms/file1
rmr: DEPRECATED: Please use '-rm -r' instead.
Deleted /kms/file1
hadoopclient> hdfs crypto -createZone -keyName key1 -path /kms
Added encryption zone /kms
hadoopclient> hdfs crypto -createZone -keyName key2 -path /kms
RemoteException: Attempt to create an encryption zone for a non-empty directory.
hadoopclient>
 

Actual Output:
===========
Exception should be Like Dir already having the ZONE will not allow to create new ZONE on this Dir

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