Mark

@kbrock @agrare Now the other jobs are running. 

@jrafanie @agrare after running the `pp ManageIQ::Providers::EmbeddedAnsible::AutomationManager::Job.find_by(:ems_ref => "66694").raw_stdout` command other stuck jobs started to work. It was stuck until then. Note: Playbook fails right now without the variables and...

@agrare Yea its reproducible. Usually when you launch multiple count of servers using a single catalog it gets stuck during ansible playbook launch.

@Fryguy In the latest version of `Narjdorf` Ansible job isn't launching at all. I see the following log entry but ansible runner isn't launching at all. `[----] I, [2022-09-05T16:20:05.401602 #324:8cdc]...

@kbrock Any idea where the code is for this issue? At least I could see if I can fix it in our env?

@agrare I'm running a method during postProvision to implement a security group. It's a method to run ansible Playbook during post provision. ``` [----] I, [2022-08-08T15:03:34.430503 #310:95b0] INFO -- automation:...

@agrare Do you still need evm.log?

@agrare I've sent you the evm.log. Can you let me know if you find anything from the last test? When I'm re-testing it's sort of this [issue ](https://github.com/ManageIQ/manageiq/issues/21972). Its not...

@agrare Increasing the Generic Worker count fixed the issue.

@Fryguy I can run playbook locally if I install packages from `requirements-azure.txt`. But when ManageIQ tries to run I get the following error `No module named azure-cli`. The import should...