Right, you're not going to get that particular error because of shell vs command. Though you should use shell for the shell operations.
What versions of Ansible are you running, what OSes are you connecting from and to? Anything particularly interesting about the sudoers configuration? On Tue, Jul 15, 2014 at 10:06 AM, Paco p <[email protected]> wrote: > I continued following the same issue: > > <192.168.1.104> ESTABLISH CONNECTION FOR USER: pi > <192.168.1.104> REMOTE_MODULE command yes | bundle exec rake gitlab:setup > RAILS_ENV=production chdir=/home/gitlab/hd/gitlab #USE_SHELL > <192.168.1.104> EXEC ['ssh', '-C', '-tt', '-vvv', '-o', > 'ControlMaster=auto', '-o', 'ControlPersist=60s', '-o', > 'ControlPath=/home/user/.ansible/cp/ansible-ssh-%h-%p-%r', '-o', 'Port=22', > '-o', 'KbdInteractiveAuthentication=no', '-o', > 'PreferredAuthentications=gssapi-with-mic,gssapi-keyex,hostbased,publickey', > '-o', 'PasswordAuthentication=no', '-o', 'User=pi', '-o', > 'ConnectTimeout=10', '192.168.1.104', "/bin/sh -c 'mkdir -p > $HOME/.ansible/tmp/ansible-tmp-1405431909.52-211323817066995 && chmod a+rx > $HOME/.ansible/tmp/ansible-tmp-1405431909.52-211323817066995 && echo > $HOME/.ansible/tmp/ansible-tmp-1405431909.52-211323817066995'"] > <192.168.1.104> PUT /tmp/tmpXQj46R TO > /home/pi/.ansible/tmp/ansible-tmp-1405431909.52-211323817066995/command > <192.168.1.104> EXEC ['ssh', '-C', '-tt', '-vvv', '-o', > 'ControlMaster=auto', '-o', 'ControlPersist=60s', '-o', > 'ControlPath=/home/user/.ansible/cp/ansible-ssh-%h-%p-%r', '-o', 'Port=22', > '-o', 'KbdInteractiveAuthentication=no', '-o', > 'PreferredAuthentications=gssapi-with-mic,gssapi-keyex,hostbased,publickey', > '-o', 'PasswordAuthentication=no', '-o', 'User=pi', '-o', > 'ConnectTimeout=10', '192.168.1.104', u'/bin/sh -c \'sudo -k && sudo -H -S > -p "[sudo via ansible, key=lvabfvouobbyzqqcpklpxtvljduerijf] password: " -u > root /bin/sh -c \'"\'"\'echo SUDO-SUCCESS-lvabfvouobbyzqqcpklpxtvljduerijf; > LC_CTYPE=C LANG=C /usr/bin/python > /home/pi/.ansible/tmp/ansible-tmp-1405431909.52-211323817066995/command; rm > -rf /home/pi/.ansible/tmp/ansible-tmp-1405431909.52-211323817066995/ > >/dev/null 2>&1\'"\'"\'\''] > > failed: [192.168.1.104] => {"failed": true, "item": "", "parsed": false} > invalid output was: SUDO-SUCCESS-lvabfvouobbyzqqcpklpxtvljduerijf > Killed > OpenSSH_6.6.1, OpenSSL 1.0.1f 6 Jan 2014 > debug1: Reading configuration data /home/user/.ssh/config > debug1: /home/user/.ssh/config line 19: Applying options for 192.168.1.104 > debug1: Reading configuration data /etc/ssh/ssh_config > debug1: /etc/ssh/ssh_config line 19: Applying options for * > debug1: auto-mux: Trying existing master > debug2: fd 3 setting O_NONBLOCK > debug2: mux_client_hello_exchange: master version 4 > debug3: mux_client_forwards: request forwardings: 0 local, 0 remote > debug3: mux_client_request_session: entering > debug3: mux_client_request_alive: entering > debug3: mux_client_request_alive: done pid = 4217 > debug3: mux_client_request_session: session request sent > debug1: mux_client_request_session: master session id: 2 > debug3: mux_client_read_packet: read header failed: Broken pipe > debug2: Received exit status from master 0 > Shared connection to 192.168.1.104 closed. > > > FATAL: all hosts have already failed -- aborting > > > El lunes, 14 de julio de 2014 21:08:28 UTC+2, James Cammarata escribió: >> >> You'll need to use the "shell:" version of the module for the piping of >> commands: >> >> - name: execute script >> shell: "yes | bash /tmp/a.sh" >> >> >> >> On Mon, Jul 14, 2014 at 9:05 AM, Paco p <[email protected]> wrote: >> >>> Hello, I need interact with a script, so I have a script as(/tmp/a.sh): >>> >>> >>> read var >>> >>> if [[ $var == "y" ]]; >>> then >>> exit 0; >>> else >>> exit 1; >>> fi >>> >>> >>> >>> >>> And in my playbook >>> >>> - name: execute script >>> command: "yes | bash /tmp/a.sh" >>> >>> >>> >>> >>> And I am getting the following: >>> failed: [192.168.1.104] => {"failed": true, "item": "", "parsed": false} >>> invalid output was: SUDO-SUCCESS-pmmitceeyaxmudspoxnoywwlhxsrkopg >>> Killed >>> >>> >>> >>> -- >>> 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/1da79ca0-c2f6-4359-b657- >>> 49757189e76c%40googlegroups.com >>> <https://groups.google.com/d/msgid/ansible-project/1da79ca0-c2f6-4359-b657-49757189e76c%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> 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/ca1421e3-b7e7-47ce-bd2f-b14a7118d3cc%40googlegroups.com > <https://groups.google.com/d/msgid/ansible-project/ca1421e3-b7e7-47ce-bd2f-b14a7118d3cc%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > 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/CA%2BnsWgwKc6fBgdJe04D6JP9H4Fm93kyVRuc-hLdjGPHvvuR0%2BA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
