Description of problem:

The CronJob for validating the license of Anaconda Professional gets automatically set to "suspended" by the operator. It means that the expected daily run is not happening. Thus, if the license expires, Anaconda does not get disabled in the dashboard as stated in RHODS docs

Prerequisites (if any, like setup, operators/versions):

Steps to Reproduce

1. Enabled Anaconda
2. Change the anaconda-ce-access secret (ns: redhat-ods-applications) to make the license key invalid (i.e., simulating the key expiration)
3. Wait some minutes after validation (5-10)
4. change the cronjob expression from 00*** to sth more close (to be run in few minutes from current time) to simulate daily run
5. check if the validation is run again (check the pods under redhat-ods-applications NS)

Step 3 is necessary because the RHODS operator takes some time to reconcile the cron job.

Actual results:

Cron Job runs only the very fist time (at activation time). It does not run daily

Expected results:

Cron Job runs daily 

Reproducibility (Always/Intermittent/Only Once):

Always

Build Details:

RHODS v1.13

Workaround:

no workaround because the operator replaces any changes we do manually

Additional info:

the field which must be set to "false" instead of "true" in the CronJob configuration is "spec.suspend". It should be set to "true" only when Anaconda is not enabled (to avoid the cron job to run continuosly when not needed)