Ansible method manageiq api_url parameter does not respect zone affinity


I am having an issue with execution of ansible methods in multizone environment.

A Generic Service is set to execute in Zone1.
Automation workflow including ansible method is executed in Zone1.
Ansible method/playbook receives manageiq.api_url parameters that points to Zone2 appliance.
Ansible method/playbook fails to contact appliance in Zone2 (isolated network).

The issues happens around 1/2 of times. I guess it just does round robin of all available workers.

I have followed @pemcg blog post to create a playbook:

It uses manageiq-core.manageiq-automate role which relies on manageiq vars. Taking into consideration that zones are isolated, it fails to connect to appliance in Zone2:

fatal: [localhost]: FAILED! => {“ansible_facts”: {“discovered_interpreter_python”: “/usr/bin/python”}, “changed”: false, “msg”: "Request failed: "}

“manageiq”: {
“X_MIQ_Group”: “admins”,
“api_token”: “token”,
“api_url”: “https://zone2_appliance_ip”,
“automate_workspace”: “automate_workspaces/d727d418-67ae-4f12-886f-ea5af313fa02”,
“group”: “groups/10000000000021”,
“request”: “requests/10000000000808”,
“request_task”: “requests/10000000000808/request_tasks/10000000001033”,
“user”: “users/10000000000002”

Any ideas?