# Subversion export via Ansible - strange error msg

**URL:** <https://forum.ansible.com/t/subversion-export-via-ansible-strange-error-msg/14960>\
**Category:** Ansible Project\
**Created:** [April 7, 2014, 5:55pm UTC](https://forum.ansible.com/t/subversion-export-via-ansible-strange-error-msg/14960 "2014-04-07T17:55:11Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jason\_Levitt](https://avatars.discourse-cdn.com/v4/letter/j/779978/32.png) [@Jason\_Levitt](https://forum.ansible.com/u/Jason_Levitt)\
**Post date:** [April 7, 2014, 5:55pm UTC](https://forum.ansible.com/t/subversion-export-via-ansible-strange-error-msg/14960/1 "2014-04-07T17:55:11Z")

</div>

Using Ansible v1.5.4, I’m trying to do a simple export of a file from SVN:

- subversion: repo=svn+ssh://theusername@svn.mysite.com/sites/svn/admin/stuff.tar.gz dest=/var/stuff export=True

The error I’m getting is:

failed: [MYVMNAME] =\> {“failed”: true, “item”: “”}  
msg: unsupported parameter for module: export

That seems to suggest that the “export” parameter of the subversion module is not supported but  
it says in the docs that it is supported at v1.5 and I’m running v1.5.4

I created the VM using Vagrant, and I’m connecting to the VM as the user “vagrant” with sudo rights and  
public key auth:

ansible-playbook -vvvvi myInventory.txt playbook.yml

Everything in the playbook.yml works fine except for the SVN export above.

In my ansible.cfg, I have:

[ssh\_connection]  
ssh\_args = -o ControlMaster=auto -o ControlPersist=60s -o ForwardAgent=yes

Here’s the output of the SVN connection:

TASK: [subversion repo=svn+ssh://theusername@svn.mysite.com/sites/svn/admin/stuff.tar.gz dest=/var/stuff export=True] \*\*\*  
\<127.0.0.1\> ESTABLISH CONNECTION FOR USER: vagrant  
\<127.0.0.1\> REMOTE\_MODULE subversion repo=svn+ssh:\*\*\*\*\*\*\*\*@svn.mysite.com/sites/svn/admin/stuff.tar.gz dest=/var/stuff export=True  
\<127.0.0.1\> EXEC [‘ssh’, ‘-C’, ‘-tt’, ‘-vvv’, ‘-o’, ‘ControlMaster=auto’, ‘-o’, ‘ControlPersist=60s’, ‘-o’, ‘ForwardAgent=yes’, ‘-o’, ‘ControlPath=/Users/someuser/.ansible/cp/ansible-ssh-%h-%p-%r’, ‘-o’, ‘Port=2222’, ‘-o’, ‘KbdInteractiveAuthentication=no’, ‘-o’, ‘PreferredAuthentications=gssapi-with-mic,gssapi-keyex,hostbased,publickey’, ‘-o’, ‘PasswordAuthentication=no’, ‘-o’, ‘User=vagrant’, ‘-o’, ‘ConnectTimeout=10’, ‘127.0.0.1’, “/bin/sh -c ‘mkdir -p $HOME/.ansible/tmp/ansible-tmp-1396892296.44-152400333196838 && chmod a+rx $HOME/.ansible/tmp/ansible-tmp-1396892296.44-152400333196838 && echo $HOME/.ansible/tmp/ansible-tmp-1396892296.44-152400333196838’”]  
\<127.0.0.1\> PUT /var/folders/lg/c\_x9gpnj3kx6ssg58nkdd2m0000nfk/T/tmp\_UeYO6 TO /home/vagrant/.ansible/tmp/ansible-tmp-1396892296.44-152400333196838/subversion  
\<127.0.0.1\> EXEC [‘ssh’, ‘-C’, ‘-tt’, ‘-vvv’, ‘-o’, ‘ControlMaster=auto’, ‘-o’, ‘ControlPersist=60s’, ‘-o’, ‘ForwardAgent=yes’, ‘-o’, ‘ControlPath=/Users/someuser/.ansible/cp/ansible-ssh-%h-%p-%r’, ‘-o’, ‘Port=2222’, ‘-o’, ‘KbdInteractiveAuthentication=no’, ‘-o’, ‘PreferredAuthentications=gssapi-with-mic,gssapi-keyex,hostbased,publickey’, ‘-o’, ‘PasswordAuthentication=no’, ‘-o’, ‘User=vagrant’, ‘-o’, ‘ConnectTimeout=10’, ‘127.0.0.1’, ‘/bin/sh -c 'sudo -k && sudo -H -S -p “[sudo via ansible, key=yzwcaybhstelqkvgejdohcxgccbuhfai] password: " -u root /bin/sh -c '”'“'echo SUDO-SUCCESS-yzwcaybhstelqkvgejdohcxgccbuhfai; /usr/bin/python /home/vagrant/.ansible/tmp/ansible-tmp-1396892296.44-152400333196838/subversion; rm -rf /home/vagrant/.ansible/tmp/ansible-tmp-1396892296.44-152400333196838/ \>/dev/null 2\>&1'”'"''’]  
failed: [MYVMNAME] =\> {“failed”: true, “item”: “”}  
msg: unsupported parameter for module: export

Anybody have any ideas about this?

-J

---

<div class="post-metadata">

**Author:** ![James\_Cammarata](https://avatars.discourse-cdn.com/v4/letter/j/7c8e57/32.png) [@James\_Cammarata](https://forum.ansible.com/u/James_Cammarata)\
**Post date:** [April 8, 2014, 3:25pm UTC](https://forum.ansible.com/t/subversion-export-via-ansible-strange-error-msg/14960/2 "2014-04-08T15:25:21Z")

</div>

This appears to be a mistake in the documentation, as the export option was actually added in the devel (1.6) branch. I will get that corrected now, thanks for catching it!