"Schedule remote Job" how to ignore failed (unresponsive) hosts when running on multible hosts

And again :wink:
Problem:
I would like to run an ansible job (I don’t want to use puppet) every 30 min only to get a report from all the registered hosts. I have created and scheduled such a job and it is running fine. If all hosts are up, the job is green and on every host dashboard the “resent jobs” list is green too.
But if a host in the list is not reachable, the whole job is shown as failed in this overview, although it was completed successfully for this host. This is unfortunately very misleading. It would be nice if only the result for this host was displayed. When I look at the whole thing under Jobs, I get the correct status displayed at the bottom for each host.
Hoped outcome:
On host page under resent jobs the result only for this host even if the job had multible target hosts

Best regards

Frank

This is a known issue Bug #35147: Recent jobs card shows failed job when it succeeded - Foreman Remote Execution - Foreman . Currently the card shows status of the entire job, not for that one particular host.

@aruzicka
thank you for the reference to the Bug. Then it’s not me :wink:

Best regards

Frank

Hello Adam, is it possible that this bug concerns the old UI and not only recent jobs card but job_invocations and template invocations screen ? This seems to be very misleading.

Could be. There is actually a different known issue[1], specific to ansible where the whole “what failed where” handling isn’t exactly great.

[1] - Bug #36130: job invocation shows wrong info after remote execution job 9regression from 6.11) - Ansible - Foreman

Well, this seems to be that mine :cry: