On Friday, March 8, 2019 at 4:12:37 AM UTC+11, Kai Stian Olstad wrote: > > On 07.03.2019 01:34, Igor Cicimov wrote: > > Anyone else seeing random playbook execution failuers like this: > > > > Source > /home/user/.ansible/tmp/ansible-tmp-1551917585.84-139567381415844/source > > not found"} > > No, you must have some issues with your setup. >
Maybe but highly unlikely. This happened during provisioning of 20 EC2 instances with same ansible config and same repository and 19 were successful but 1 failed with the error. All instances autoprovision them self locally and the one that failed has hundreds of tasks successfully executed before the failed one. I remember seeing an issue where the OP found out that the: remote_tmp = $HOME/.ansible/tmp settings works unreliably and ansible looses the tmp path being unable to resolve the $HOME env var. I tried googling it up again but can not find it now :-/ > > > Any idea what is causing them and how to fix it? > > Running with -vvvv might give you some more information. > That's hard since replaying the whole playbook several times after the failure shows no issues at all. > > -- > Kai Stian Olstad > -- 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/b59d4be9-4ec8-418e-87ee-f18a6e08fa16%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
