Running 2.10.1 version of stackstorm and 2.7.5 python on CentOS Linux release 7.6.1810 in K8s, using mistral workflow. We directly run the workflow, and it works properly, we go to rules and try to schedule using a cron timer or interval timer and the workflow kicks off as expected and stays in running state, never progressing or failing, never even running the first task. Its still hanging around 24 hours later. This appeared after upgrading from 2.9.x to 2.10 version. Verified the scheduler is running and we see the execution starting in the mistral logs.
I noted that I cannot reproduce on a single node instance, but running in K8s we are seeing this issue. It appears it may be related to using Helm charts for the mistral workflow?
OK another update, when running as a rule, we are running as a different user, which does not have correct permissions it appears. We have this working now, using LDAP authentication, we add the required user stanley and now we can schedule workflows using rules.