User add playbook question - something is wrong and I don't know what

[Brian Dunbar]

I have a playbook, the task consistently flags one user as 'ok' and one user as 'changed'. 

See this gist: https://gist.github.com/bdunbar/ec35fb02d4147ad1f5b5

Why is this?  Clearly the user already exists, so it _should_ be 'ok' and not 'changed'.

I'm doing something wrong, and I'd like to know what that is.

Thanks!

~brian

[Michael DeHaan]

How are the systems different?

--
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.
To post to this group, send email to ansible...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/f587b428-7d88-4e91-bec6-35751067ae4d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Brian Dunbar]

I'm running the playbook against the same host, 'sftp' each time.

'aws-stage-sftp' is Ubuntu 12.04.4 LTS

# inventory.yml

(snip)

aws-stage-sftp         ansible_ssh_host=11.11.11.11

(snip)

[sftp]

aws-stage-sftp

[Scott Sturdivant]

Just a guess, but since both users are pointing at the same home dir, but have different UID/GIDs, is it possible that ansible is chowning '/home/sftp' ?  Although if that were the case, I'd expect both the tasks in subsequent runs to report as 'changed'...

To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/616ca0e4-4433-4d02-a1b6-39a5e3e12f1c%40googlegroups.com.

[Brian Dunbar]

On Wednesday, May 28, 2014 12:47:09 PM UTC-5, Scott Sturdivant wrote:

Just a guess, but since both users are pointing at the same home dir, but have different UID/GIDs, is it possible that ansible is chowning '/home/sftp' ?  Although if that were the case, I'd expect both the tasks in subsequent runs to report as 'changed'...

Bar the chowning, that makes sense.  They both have the same homedir because they're jailed 'demi-root' users. 

I should probably did into the users module in the code and see what it's _actually_ doing in there.