Plugins » Ansible

How reproducible:
Always

Steps to reproduce:

1. Schedule Job
2. Ansible Commands + Run Command (e.g. whoami)
3. Under SSH User, set a user that is different from the global one or the one set in the parameter remote_execution_ssh_user
4. Run the job

Result:
Ansible still tries to connect using the host parameter or the global setting and completely ignores the setting in the advanced field of the job.

You can check this for example by looking at /var/log/secure on the target host.

Expected result:
I expect the advanced field in the job invocation to have the highest priority. It should override the remote_execution_effective_user host parameter and the corresponding global settings if they are present.

Additional Info:
I am aware of Issue n. 36448. It looks possibly related, but I cannot reproduce it (the effective user is NOT ignored for me, only the SSH user).