Date: Fri, 22 Jan 2016 16:32:04 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 206498] sysutils/ansible -- tries to feed sh-syntax commands to csh Message-ID: <bug-206498-13@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D206498 Bug ID: 206498 Summary: sysutils/ansible -- tries to feed sh-syntax commands to csh Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: Individual Port(s) Assignee: freebsd-ports-bugs@FreeBSD.org Reporter: matthew@FreeBSD.org CC: lifanov@mail.lifanov.com Flags: maintainer-feedback?(lifanov@mail.lifanov.com) CC: lifanov@mail.lifanov.com Created attachment 165964 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D165964&action= =3Dedit Derived from upstream commit 8647fdc7f25ba1c707c5333ca1581a1fa0ffe566 Seems there's a show-stopper bug in the latest ansible port: % ansible -vvv stingray.fish.adestra.com -m setup Using /usr/local/etc/ansible/ansible.cfg as config file <stingray.fish.adestra.com> ESTABLISH SSH CONNECTION FOR USER: None <stingray.fish.adestra.com> SSH: EXEC ssh -C -q -A -o ControlMaster=3Dauto = -o ControlPersist=3D60s -o Port=3D22 -o KbdInteractiveAuthentication=3Dno -o PreferredAuthentications=3Dgssapi-with-mic,gssapi-keyex,hostbased,publickey= -o PasswordAuthentication=3Dno -o ConnectTimeout=3D10 -o ControlPath=3D/home/matthew/.ansible/cp/ansible-ssh-%h-%p-%r -tt stingray.fish.adestra.com '( umask 22 && mkdir -p "$( echo ${HOME}/.ansible/tmp/ansible-tmp-1453477395.69-234719990038675 )" && echo "= $( echo ${HOME}/.ansible/tmp/ansible-tmp-1453477395.69-234719990038675 )" )' stingray.fish.adestra.com | UNREACHABLE! =3D> { "changed": false, "msg": "ERROR! Authentication or permission failure. In some cases, you may have been able to authenticate and did not have permissions on the remote directory. Consider changing the remote temp path in ansible.cfg to a path rooted in \"/tmp\". Failed command was: ( umask 22 && mkdir -p \"$( echo ${HOME}/.ansible/tmp/ansible-tmp-1453477395.69-234719990038675 )\" && echo = \"$( echo ${HOME}/.ansible/tmp/ansible-tmp-1453477395.69-234719990038675 )\" ), exited with result 1: Illegal variable name.\r\n", "unreachable": true } On FreeBSD machines, where root's shell is by default /bin/csh, ansible end= s up using that trying to run commands with /bin/sh syntax. Which simply doesn't work. This has been reported upstream (Issues: #13745, #13882) and this fix has b= een committed to ansible github: https://github.com/ansible/ansible/commit/8647fdc7f25ba1c707c5333ca1581a1fa= 0ffe566 Would it be possible to add this as a patch to the ansible FreeBSD port unt= il the next release comes out? poudriere testport: OK --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-206498-13>