Ansible-Pull Copy Error

[Paul Truzzi]

I was following a tutorial from a year ago so perhaps something in Ansible has changed.  My issue is I get this error:

TASK [copy sudoers_ansible] ****************************************************
fatal: [localhost]: FAILED! => {"changed": false, "checksum": "9c9e5aae4aa1c02a4934d7172d2c4cd6c057d15d",  "msg": "Unsupported parameters for (ansible.legacy.copy) module: root Supported parameters include:
 _original_basename, attributes, backup, checksum, content, dest, directory_mode, follow, force, group, local_follow,  mode, owner, remote_src, selevel, serole, setype, seuser, src, unsafe_writes, validate"}

From my users.yml file I have the following:

- name: copy sudoers_ansible
  copy:
    src: files/sudoers_ansible
    dest: /etc/sudoers.d/ansible
    owner: root
    group: root

    mode: 0440

I've added ansible as a system sudoer. All of the parameters I'm using; src, dest, owner, group and mode seem to be listed as supported in the error message.

[Dick Visser]

Are you sure this is the task that is being run?

Try adding an extra bogus parameter, that should then be listed in the error message

--
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 view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/f14aa3ba-47e1-479e-9b7b-568c0e741312n%40googlegroups.com.

--

Sent from a mobile device - please excuse the brevity, spelling and punctuation.

[Paul]

I added a bogus parameter to my users.yml file as follows;

- name: copy sudoers_ansible
  copy:

    bogus: parameter

    src: files/sudoers_ansible
    dest: /etc/sudoers.d/ansible
    owner: root

    root: root
    mode: 0440

Now the error message reads:

TASK [copy sudoers_ansible] ****************************************************
fatal: [localhost]: FAILED! => {"changed": false, "checksum": "9c9e5aae4aa1c02a4934d7172d2c4cd6c057d15d", "msg": "Unsupported parameters for (ansible.legacy.copy) module: bogus, root Supported parameters include: _original_basename, attributes, backup, checksum, content, dest, directory_mode, follow, force, group, local_follow, mode, owner, remote_src, selevel, serole, setype, seuser, src, unsafe_writes, validate"}

PLAY RECAP *********************************************************************
localhost                  : ok=3    changed=0    unreachable=0    failed=1    skipped=0    rescued=0    ignored=0   

I also verified that the destination file "/etc/sudoers.d/ansible" does not exist. The source file "~/git projects/ansible_pull/tasks/files/sudoers_ansible"  does exist.

Paul

You received this message because you are subscribed to a topic in the Google Groups "Ansible Project" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/ansible-project/E2nR8v37D20/unsubscribe.
To unsubscribe from this group and all its topics, send an email to ansible-proje...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/CAL8fbwP7mb_j%3Dz06C8MAgLfXwjW1717bBZ4o5g4vjj6qsf5HEA%40mail.gmail.com.

[Dick Visser]

On Thu, 4 Nov 2021 at 00:37, Paul <paul....@gmail.com> wrote:

I added a bogus parameter to my users.yml file as follows;

- name: copy sudoers_ansible
  copy:
    bogus: parameter
    src: files/sudoers_ansible
    dest: /etc/sudoers.d/ansible
    owner: root
    root: root

There is your issue. 

You didn't post this in the first place?

To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/20331b65-3c18-75a0-248a-e35f8b92f190%40gmail.com.

[Paul Truzzi]

OK, I'm lost. What is my issue? The formatting of  your reply is a bit funky. But if you are talking about "mode: 0440", that was in the initial post. Is there something wrong with that, and if so, what?

To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/CAL8fbwNmgumY8gNWGfZE_uxZFAFiRb4_ceQPm3UFMfG7sxZ9Kg%40mail.gmail.com.

[Felix Fontein]

Hi Paul,

he was talking about the line **above** what he wrote, which is 'root:
root'. That line was **not** included in your first post, and that's
the line that's wrong. It must be 'user: root' (as it was in your first
post).

> >     root: root

Cheers,
Felix

[Paul Truzzi]

I must have been reviewing the wrong file, not the one that was being executed, because it said group: root. But the actual users.yml did have root: root and now  it works as expected.

Sorry, for MY confusion.