my first reaction would be to suggest looking into "until" loop structure. if your module can query for results reutrning some value, until will keep calling it until N retries run out or module will execute successfully
On Wednesday, October 24, 2018 at 1:21:19 PM UTC-7, rd wrote: > > Hello, > > I have a use case where I need drop a long running command(x1) on a remote > host and then track its status via another command(x2). > I have tried doing that using async with Poll "0" for x1 command , and > then run retries for the other command(x2) until i see a certain output. > > > My questions: > > 1) Is there another alternate to use using retries in this case? > > 2) Is there a way to: > > 1. Change the "FAILED RETRYING" to a custom message?... > please note I am using a shared environment and have no flexibility to > modify the actual ansible configuration. > 2. Display STDOUT from each retry show along with "FAILED > RETRYING" ? > > > Please let me know if I can provide any other details. > Any assistance is greatly appreciated. > > > thanks > Rd > -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/a635c35a-b221-439c-ba98-9dc853c88cee%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
