Affects Version/s: 3.0.0
Fix Version/s: None
3 node SUSE linux cluster
No administrative command provided to delete an user defined erasure coding policy
Step : -
- Create a Directory
- Add 64 user-defined ec policies in the ID range of [64 to 127].Beyond that system will not allow
to add any more policy.
- Enable an ec policy and the set it to the directory.
- Disable the policy and check the state of the policy in -listPolicies
-If the ec policy is in disable state ,system will not allow you to set it on any directory
-Remove the ec policy and check the state of the policy in -listPolicies.
Its just set the state as removed ,but the policy is still present in the list.
-If the ec policy is in remove state,system will not allow you to set it on any directory
- There is no difference between disable and remove state.
-After adding 64 user-defined ec policies ,if an user wants to delete a policy which is not usable any more or not correctly added instead of that wants to add a new desired user-defined ec policy ,it can not be possible as no delete option is provided.Only remove policy option is given,which is not removing an user-defined policy,only set the policy state as removed.
Actual ouput :-
No administrative command provided to delete an user defined erasure coding policy.With "-removePolicy" we can set a policy state as removed,we cann't delete the user-defined ec policy.After adding 64 user-defined ec policies,if a user wants to delete an policy and add a new desired policy,there is no administrative provision provided to perform this operation.
Expected output :-
Either "-removePolicy" should remove the user-defined ec policy ,instead of changing the policy state to removed only or administrative privilege should be provided to delete an user-defined ec policy.