Ah ok, yeah I didn't see the above answer in the response on the issue ... I'm surprised this isn't a faq.
Thanks, Ben On Fri, May 8, 2015 at 5:27 PM, Brian Coca <[email protected]> wrote: > hi, im the bot that closed the issue, in the response you might have > missed the answer: > > set ansible_shell_type=csh group/host var for this host and > checksumming should work again. Different shell families need > different quoting. > > On Fri, May 8, 2015 at 8:25 PM, breatheoften <[email protected]> wrote: > > I created an issue reporting what appears to me to be a bug in the fetch > > module -- the fetch module succeeds in grabbing the remote file and then > > always fails its checksum test if the remote user's login shell is set to > > /bin/tcsh -- but works when the remote user's login shell is set to > > /bin/bash. > > > > I filed an issue along with simplified steps to reproduce: > > > > > https://github.com/ansible/ansible-modules-core/issues/1297#event-300717455 > > > > The issue was closed (by a bot?) -- with a note pointing me at this list. > > > > Is this a user issue or a bug? I'm not seeing any documentation that > > implies that the remote_user's login shell needs to be bash ... Is that > a > > requirement of ansible? This requirement is not described in the faq or > any > > documentation that I find ... I can't think of anything about my bug > report > > that implies this is a user support issue. > > > > The fetch module behavior is broken when the remote user's login shell is > > set to /bin/tcsh. That seems an awful lot like a bug to me ... > > > > I've been using ansible for awhile now -- usually the remote_user's login > > shell has always been bash -- but in some cases, some of these hosts have > > had their login shells changed and I can't necessarily immediately change > > them back to bash. > > > > Thanks, > > Ben > > > > -- > > 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/09e25c17-b319-4e20-bd2a-597e4465b939%40googlegroups.com > . > > For more options, visit https://groups.google.com/d/optout. > > > > -- > Brian Coca > > -- > 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/CAJ5XC8kvdRMdiRtswYkrQifsScVcrZwxgk8ZTxSra04bt%3DtUyQ%40mail.gmail.com > . > For more options, visit https://groups.google.com/d/optout. > -- 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/CABUBibv12q8YSKAr1%2B-mnSmT%3D8hhmj2rc%3DGYKpVWjuoHVSS%2Bgw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
