Let us know what remote OS that triggered the problem on for starters. If it's resolved in 1.5, getting that update out should resolve most things -- I haven't heard a lot of reports of this, and it's pretty safe to run 1.5 at this point. Won't always be the case, but we're getting this ready to go for release and this release has been mostly focused on bugfixes and module additions other than the addition of vault.
(See https://github.com/ansible/ansible/blob/devel/CHANGELOG.md) On Wed, Feb 19, 2014 at 7:58 AM, Marc Patermann < [email protected]> wrote: > Michael DeHaan schrieb (19.02.2014 13:54 Uhr): > > Yes, please let us know if it does. >> > OK, I'm trying to build a RPM from 1.5.0-pre and will report back. > > > I'm pushing for 1.5 to release a bit sooner (weeks) actually. >> >> I'd be interested in the remote OS and conditions that triggered this >> situation. >> > What can I do to help? > > > Marc > > -- > 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]. > For more options, visit https://groups.google.com/groups/opt_out. > -- 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]. For more options, visit https://groups.google.com/groups/opt_out.
