If you change the JT whitelist while a workflow is running (and restart Oozie), that workflow will stay RUNNING forever. The correct behavior should be the same as if the JT is unavailable: Oozie retries a few times and SUSPENDs the workflow. Then the user should either put it back into the whitelist and resume, or simply kill it.
There might be multiple ways to reproduce, but here's one:
- Submit a workflow that has enough actions to run for a while
- Suspend the workflow
- Change the JT whitelist
- Restart Oozie
- Resume the workflow
You'll get errors about the whitelist, but it won't ever transition out of RUNNING