Hey Chip, I can confirm that the unarchive module is not handling the tilde correctly in 1.7.2 and the bug is fixed in the devel branch.
The following two commits implemented the fix: https://github.com/ansible/ansible/commit/bc4272d2a26e47418c7d588208482d05a34a34cd https://github.com/ansible/ansible/commit/565e5bbdfc42afe29c4f53b303352d7e8406dcba We're hoping to have 1.8 out very soon which should have the fix in it. -Toshio On Thu, Nov 20, 2014 at 5:07 PM, Chip Selden <[email protected]> wrote: > Toshio, > > I am currently using 1.7.2 > > The text above should be enough of a playbook for you to reproduce the > issue. Here it is again below. Just use any host, user and zip file you have > to try it out. The issue occurs when unarchiving into the host "dest" > directory which doesn't exist because the tilde was evaluated as the home > directory of the master server (for that reason, make sure the home > directories of your master and host are not the same). > > --- > - hosts: [somehost] > vars: > mydir: "~/folder/subfolder/" > user: [someuser] > tasks: > - name: Ensure the parent directory is present > file: > > path={{ mydir }} > state=directory > - name: Unzip the file into the host > unarchive: > > src=/some/master/directory/file.zip > dest={{ mydir }} > > On Thursday, November 20, 2014 10:28:11 AM UTC-5, tkuratomi wrote: >> >> Do note, there were some places in the code that mistakenly expanded the >> tilde on the ansible controller side that were fixed recently. Are you >> using ansible 1.7.2 or are you using a checkout of development? If you can >> give us a minimal playbook to reproduce I could see if it has been fixed. >> >> -Toshio >> >> On Nov 19, 2014 10:20 AM, "Brian Coca" <[email protected]> wrote: >>> >>> I'm sorry, I misunderstood, unarchive should never resolve on master the >>> 'dest' unless it is also the target. >>> >>> >>> >>> -- >>> 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/CAJ5XC8%3DvPofEx4whV%3Df0wcj5s7HLdN6h%3DoZCZ3LpNmANBy4fUQ%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/5cd98f33-cc03-4cca-b670-c763a638275f%40googlegroups.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/CAG9juEpbAvP-4fFaOOB2OiA6He0m2Q1CU04ky_%3DSX_MJBpcAtg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
