Not sure it makes any difference but can you try to use the colon yaml
syntax for the parameters

On Thu, 20 Aug 2020 at 21:34, Martey Dodoo <[email protected]> wrote:

> Hi everyone,
>
> I'm having some issues using the "mode" parameter on the file module
> <https://docs.ansible.com/ansible/latest/modules/file_module.html#parameter-mode>
> to change ownership of an existing directory without modifying its
> permissions. For example:
>
> > - name: use preserve mode
> >   file:
> >     path=/tmp/test
> >     owner=www-data
> >     mode=preserve
> >     state=directory
> >   become: true
>
> Based on the documentation, I would assume that this would "preserve" the
> directory's existing permissions while changing its owner. Instead, it
> fails with "mode must be in octal or symbolic form" / "bad symbolic
> permission for mode: preserve".
>
> I've managed to get the behavior I need by using an empty string for the
> mode parameter, but I am unsure why "preserve" doesn't work. Is this a bug
> in the file module? Am I reading the documentation wrong?
>
> Thanks,
> Martey
>
>
>
>
>
>
>
>
> --
>
>
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/ansible-project/74a54f7c-bfa3-4dd4-a992-b4804ecf6e19n%40googlegroups.com
> <https://groups.google.com/d/msgid/ansible-project/74a54f7c-bfa3-4dd4-a992-b4804ecf6e19n%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>
>
> --
Sent from a mobile device - please excuse the brevity, spelling and
punctuation.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAL8fbwPrUiPyk4u%2BjxQnzL40tLxkg9qWesP4Y3hcWY%2BQniJ1Fg%40mail.gmail.com.

Reply via email to