Ansible contains some fuzzy logic for this. Basically, if the number is a string, it will assume octal.
If you pass in a decimal, as you have done above, it will assume you know what you are doing. (Most people use short-form arguments in Ansible, here you've split to another line and passed a decimal - which is fine). So yes, this would be it. Alternatively, this would also fit: mode: "777" On Sun, Aug 10, 2014 at 6:39 PM, Greg Andrews <[email protected]> wrote: > > There's no leading "0" on your mode number 2770. In Perl, the run-time > parses numbers as decimal unless they have certain hint prefixes, like "0x" > for hexadecimal and "0" for octal. > > I don't know how Python parses numbers, but 2770 decimal = 5322 octal, so > it looks like that may be the source of the confusion. The ansible.com > docs for the file module don't address this explicitly, but both the > examples have a leading "0" in the mode number. It looks to me like a mode > number of "02770" is what you need. > > -Greg > > > > On Sun, Aug 10, 2014 at 10:00 AM, Deon Bredenhann <[email protected]> > wrote: > >> - name: Create test >> file: >> path: /srv/test >> state: directory >> mode: 2770 >> owner: root >> group: admin >> >> Output of -v >> {"changed": true, "gid": 6003, "group": "admin", "mode": "05322", >> "owner": "root", "path": "/srv/test", "size": 4096, "state": "directory", >> "uid": 0} >> >> So the mode of 2770 somehow gets converted to 05322 >> >> So any mode with SetGID, SetUID or SetSticky, gets mangled. >> Tried in 1.6 and 1.7 >> >> 1770 -> 03352 >> 2770 -> 05322 >> 4770 -> 01242 >> >> I should convert the end permissions to octal and see if there is a >> pattern. Will do later. Just want to post this for now and see if someone >> knows anything about this. >> >> Thanks >> Deon >> >> -- >> 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/36ed2d34-e94d-475f-b8a8-a1a00631fdd5%40googlegroups.com >> <https://groups.google.com/d/msgid/ansible-project/36ed2d34-e94d-475f-b8a8-a1a00631fdd5%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> 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/CAPdwyX6ka_TymsSuJqdp0UijOwrAsT8_K%3DVQbu3tqEiM%3Dk57hA%40mail.gmail.com > <https://groups.google.com/d/msgid/ansible-project/CAPdwyX6ka_TymsSuJqdp0UijOwrAsT8_K%3DVQbu3tqEiM%3Dk57hA%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > > 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/CA%2BnsWgzQHqPnNVUU%3DgUCMhmzSinAGSbSAOVh9VuGP0%3DT3gYbmg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
