Bug 2293621

Description of problem (please be detailed as possible and provide log
snippests):

Rook has a bug related to encryption key rotation.
The case is actually very hard to hit.
When this particular bug is hit, the key rotation jobs will start to fail.
There is no risk to OSD data.

```
While adding a new encryption key to slot 1
if there exists a key in slot 1 which is not
equal to the one we want to update it with,
we kill the slot and then add the new key to it.

While killing the slot, the existing code uses
the new key, which is not valid in such cases.

This patch modifies the code to use the key in
slot 0 (the one that we know works) to kill the slot.
```




Is there any workaround available to the best of your knowledge?
manually delete fetch key from kms and delete keyslot 1. 


Rate from 1 - 5 the complexity of the scenario you performed that caused this
bug (1 - very simple, 5 - very complex)?
5

Can this issue reproducible?
Very difficult to reproduce from manual deletion of key rotation jobs.
The job has to be deleted right before a particular step which is nearly impossible

Can this issue reproduce from the UI?
no

If this is a regression, please provide more details to justify this:
not a regression.

Steps to Reproduce:
1.
2.
3.


Actual results:


Expected results:


Additional info: