We got a lot of heavy rain last night, and this morning I noticed this 2" flotilla of springtails in the drip tray for my avocado sapling. I'm assuming they were washed out of the pot, so I scooped them up to redeposit them back in the plant.
Please help take care of my plant little guys!
I've got a playbook that does some evaluations on hosts and then does an import_playbook for a reboot. I do this so I can change the strategy of the reboot on hosts to free, and they can take care of it in their own time, not waiting for the other hosts to finish.
It seems when you use the free strategy that the task name won't display until a host has something to report. So when the reboot module task actually starts, there's no task name displayed and it kind of looks like the play just freezes up until one of the hosts finishes the reboot and responds again. So I'd like to post a message for the user running the playbook not to panic, and just wait for a bit.
I know I can just use debug and print a message, with run_once, but it just looks a bit sloppy. I'm just being a stickler here, but I really like the idea of a blank "comment" task, where it just displays the typical:
TASK [This is the task name] *********************
The meta module has noop, which displays the task name, and that's it. it's perfect, but for some reason it runs for every host, even though it has the bypass_host_loop attribute. Even when I use run_once: true, it still repeats for each host. If I use the free strategy, it doesn't seem to run at all, which I see is also because of the bypass_host_loop attribute.
Likewise, even run_once with the debug isn't honored when using the "free" strategy.
So does anyone know how I can possibly display a quick simple note for the user just before the reboot task starts given the scenario?