On Wednesday, August 27, 2014 5:21:24 PM UTC-7, Michael DeHaan wrote:
>
> Hi,
>
> Please make sure you are on the most recent version of Ansible if asking 
> questions to this list.  Many things have changed or been improved in 
> various releases, and it's quick to upgrade.
>
> The current latest version is 1.7.1.
>

This is excellent advice. You're absolutely right. I just upgraded. 

I believe the chown attempts as non-root has already been addressed.
>
 
It doesn't look this way. This is on a host where /etc/ansible/hosts 
contains

[all]
localhost

$ ls -l /tmp/jon
ls: cannot access /tmp/jon: No such file or directory

$ ansible --version
ansible 1.7.1

$ ansible all -m file -a 'path=/tmp/jon state=touch mode=0644 owner=root'
localhost | FAILED >> {
    "failed": true,
    "gid": 1000,
    "group": "jonf",
    "mode": "0664",
    "msg": "chown failed",
    "owner": "jonf",
    "path": "/tmp/jon",
    "size": 0,
    "state": "file",
    "uid": 1000
}

$ ls -l /tmp/jon
-rw-rw-r-- 1 jonf jonf 0 Aug 27 18:07 /tmp/jon

This is the same behavior as with 1.6.6. After Ansible runs '/tmp/jon' 
exists with the wrong owner.
Don't you think it should exist with the correct owner or it shouldn't 
exist at all?

Jon

-- 
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/1b1c5225-1dd7-4ed7-8d19-8d7061392869%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to