Problem:
In testing Foreman/Katello in our space, I was curious if jobs would be “picked up” by hosts when they became available, as we regularly have hosts offline/online at random. So I chose 2 hosts, powered one off, and pushed an SSH script. One succeeded, one timed out and permanently ended the task/job. Powering up the second host resulted in no action (As expected after seeing the timeout in Foreman).
I looked at job options and saw “Schedule Future Execution” and “Recurring execution”. Neither seem to be what I need.
Expected outcome:
One succeed. The second stays incomplete until it powers up, checks in with Foreman, completes the task.
Interface of Foreman shows 50% completion until second host wakes up and does it task, then Foreman shows 100% completion.
If second host never wakes up, Foreman shows 50% completion forever.
Foreman and Proxy versions:
Latest I believe (2.3.5)
Foreman and Proxy plugin versions:
|foreman-tasks |3.0.6|
|foreman_remote_execution |4.2.2|
|katello |3.18.5|
Distribution and version:
Not sure
Other relevant data:
Hosts are CentOS7
I’m still learning, here. Our end goal is to find a replacement for Spacewalk. So far Foreman/Katello is the most promising.