Description of problem: When remote execution job is started by webhook, connect by ip parametre is ignored. This is issue in environment without DHCP when job fails since it can not resolve the target Version-Release number of selected component (if applicable): 6.10.5.1 How reproducible: 100% Steps to Reproduce: 1. create a ansible job 2. create webhook Administer > Webhooks Templates. 3. create condition that executes webhook Actual results: Job fails and ignores connect by ip parametre Expected results: Job executes successfully Additional info:
Recapturing what I said on last week's meeting. There is no way how you can toggle connect_by_ip per job, no matter if you use ui or api, it is not exposed. The working hypothesis right now is that by triggering a job so shortly after the host is created, the job starts running before all the host's associations are fully saved. In the excerpts in the case we can see connect_by_ip is always true and apparently host's interfaces do not have ip set at that time (search for "ip:") so it falls through to hostname. To be able to confirm or refute this, we need logs. A sosreport from may is not enough and task exports are not enough in this case. Of course, the more verbose the logs the better. On a side note, why do this through webhooks? Why not just turn the thing to be run into a role and assign it to a host? It should then run automatically post-provisioning.
Revisiting this, the title is misleading. Remote execution does not (and possibly even cannot) ignore the setting/parameter, in this case the job is triggered before the host has ip addresses set on its interfaces, which is entirely different bug altogether and cannot be solved in remote execution itself. @Stefan Do we know if the host in question was provisioned, registered or just created by Satellite receiving facts?
Flipping over to hooks, firing an event when a host is *completely* created/updated would most likely make this go away.