EOF in backquote substitution

[Paul Hassinger]

I am receiving the following with verbose debugging:

<myserver.mydomain.com> ESTABLISH CONNECTION FOR USER: cq
<myserver.mydomain.com> EXEC ['ssh', '-tt', '-q', '-o', 'ControlMaster=auto', '-o', 'ControlPersist=60s', '-o', 'ControlPath=/tmp/ansible-ssh-%h-%p-%r', '-o', 'Port=22', '-o', 'KbdInteractiveAuthentication=no', '-o', 'PasswordAuthentication=no', '-o', 'User=cq', '-o', 'ConnectTimeout=10', 'myserver.mydomain.com', "/bin/sh -c 'mkdir -p /home/ipauldev/.ansible/tmp/ansible-1373558723.98-238619182609175 && chmod a+rx /home/ipauldev/.ansible/tmp/ansible-1373558723.98-238619182609175 && echo /home/ipauldev/.ansible/tmp/ansible-1373558723.98-238619182609175'"]
<myserver.mydomain.com> REMOTE_MODULE setup  CHECKMODE=True
<myserver.mydomain.com> PUT /tmp/tmp90a9wE TO mkdir: cannot create directory `/home/ipauldev': Permission denied/setup
<myserver.mydomain.com> EXEC ['ssh', '-tt', '-q', '-o', 'ControlMaster=auto', '-o', 'ControlPersist=60s', '-o', 'ControlPath=/tmp/ansible-ssh-%h-%p-%r', '-o', 'Port=22', '-o', 'KbdInteractiveAuthentication=no', '-o', 'PasswordAuthentication=no', '-o', 'User=cq', '-o', 'ConnectTimeout=10', 'myserver.mydomain.com', '/bin/sh -c \'/usr/bin/python mkdir: cannot create directory `/home/ipauldev\'"\'"\': Permission denied/setup\'']

failed: [myserver.mydomain.com] => {"failed": true, "parsed": false}
invalid output was: /bin/sh: 1: Syntax error: EOF in backquote substitution

I did update to the latest source from github... not sure if that, or something else on my end changed... I see it's looking at permission denied issues as well.

Looking for any ideas/assistance.

Thanks in advance.

[Paul Hassinger]

It looks like this commit causes this issue:

https://github.com/ansible/ansible/commit/e5ff35bbdb84b70e7bfa13398b296f15089aaa48

[Michael DeHaan]

Please don't comment on commits but rather file bugs instead, comments on commits are just going to be lost in the shuffle.

Can you share the command you ran in the playbook that caused this problem?

Thanks!

On Thu, Jul 11, 2013 at 12:25 PM, Paul Hassinger <hassing...@ipaul.com> wrote:

It looks like this commit causes this issue:

https://github.com/ansible/ansible/commit/e5ff35bbdb84b70e7bfa13398b296f15089aaa48

--
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 ansible-proje...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--

Michael DeHaan <mic...@ansibleworks.com>
CTO, AnsibleWorks, Inc.
http://www.ansibleworks.com/

[Andreas Piesk]

On 11.07.2013 18:25, Paul Hassinger wrote:
> It looks like this commit causes this issue:
>
> https://github.com/ansible/ansible/commit/e5ff35bbdb84b70e7bfa13398b296f15089aaa48
>

i think, the commit itself isn't the problem but it reveals a bug, IMHO.
as far as i understand it remote_tmp is supposed to be expanded by the
shell on the remote side.
that means, remote_tmp shouldn't be expanded at all by ansible because
without the commit a path like '~/.ansible/tmp' would lead to the same
issue too.

-ap

[Michael DeHaan]

I've reverted this one, thanks!

Basically we need a param on shell_expand_path and should not call it on the remote temp parameter

If you can make this change we can add in expansion on other parameters back in.

Thanks!

--
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 ansible-project+unsubscribe@googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.

[Paul Hassinger]

OK, thanks. I will not comment on the commits in the future, thank you.

The issue failed on gathering facts, no specific command in the playbook. (I tried removing a couple of tasks, it just always fails for me)

Would you still like me to file a bug? or are we good since you reverted the commit? I assume AlphaPapa101 will handle that...

[Michael DeHaan]

I think we are ok because we reverted it, but a pull request to fix up the others from A.P. would be great!