forked from rook/rook
There is a corner case where an env variable populated with the prepare job could influence and trigger some encryption code. We have an env variable to discover whether the prepare job will encrypt a drive or not so let's use that instead of running code as a noop and sometimes trigger a corner case. In this scenario, the prepare job had an "IBM_" env variable present in the OS image (IBM OS) so the setKEKinEnv() function would get called for no reason. Signed-off-by: Sébastien Han <seb@redhat.com>