"ansible --version" no longer reports the version of the "ansible"
plugin. The version of the software no longer has anything to do with
the version of the pypo.org published tarball, it's confusing for
everyone. To check this, use "pip list | grep ansible" or "pip3 list |
grep ansible", depending on your operating system's base version of
python.

    ansible < 2.10 actually contains the ansible software
    ansible >= 2.10 does not contain the ansible software, the name is
very confusing.

    ansible-core >= 2.10 actually contains the critical software but
is published via a pypo.org tarball with a new name.
        https://github.com/ansible/ansible/ no longer contains the
tools for the "ansible" tarball at pypi.org
    That git repo now contains ansible-core source code
    To install ansible commands, use "pip install ansible-core"
    Nearly all python requirements need to reset their
requirements.txt as "ansible-core" to get the working ansible python
modules..

This is confusing as hell. I'd love to see the notes or minutes from
whatever committee decided to do this, but I've asked and it is not
available.

    ansible > 2.9,< 4.0 not worth the cycles to a lot has been revised.

    ansible >= 4 is now purely a collection of ansible galaxy modules.
A modest few of them were formerly in the basic ansible github repo.
        https://github.com/ansible-community/antsibull now contains
the tools for building ansible tarballs for pip install
        https://github.com/ansible-collections/ now contains the
source for most of these ansible galaxy modules
   ansible >= 4 does not contain the ansible software. It requires
"ansible-core", which does.
        The claim published with ansible releases that it "includes"
the functional ansible tools is misleading, the correct preposition is
"requires". The working software is actually in the "ansible-core"
python module.
    ansible == 4 is huge, more than 400 MBytes of installed modules,
including more than 100 distinct ansible galaxy modules, very few of
which are commonly used and most of which are useful for most ansible
servers.
    ansible >= 4 modules all listed among python modules as
"aws_collections" , generally referenced by ansible using the ansible
galaxy tools rather than as standard python modules.
    ansible >= 4 modules are available individually with the "ansible
galaxy" galaxy commands, installed individually and updated or
reverted individually.
        The "ansible galaxy" command does not install individual
modules in the same location, it publishes them in /usr/share rather
than /usr/lib/python/

This is very confusing. Even Red Hat has not been able to keep their
documentation consistent about this, and they bought ansible.com back
in 2015. And the release announcements claiming that ansible-core is
"included" make it more confusing.

As a user of ansible, someone who's set up several Ansible Tower and
AWX servers myself, I'm game to support update paths. My RPM building
tools for RHEL systems are available over at:

    https://github.com/nkadel/ansiblerepo/

Nico Kadel-Garcia
Email: [email protected]

On Thu, Dec 23, 2021 at 1:51 AM Dick Visser <[email protected]> wrote:
>
> What is the output of
>
> ansible --version
>
> ?
>
> On Thu, 23 Dec 2021 at 00:29, nishant shah <[email protected]> wrote:
>>
>> THanks Felix for quick response. It is still giving an error Method not 
>> found-
>>
>> I updated my playbook-
>> [root@localhost ansible-content]# cat playbook-Create_User.yml
>> ---
>> - name: Create new user account
>>   hosts: all
>>   tasks:
>>     - junipernetworks.junos.junos_user:
>>         name: testusr
>>         role: super-user
>>         state: present
>>
>> It is giving error as-
>>
>> [root@localhost ansible-content]# ansible-playbook playbook-Create_User.yml
>> [WARNING]: ansible.utils.display.initialize_locale has not been called, this 
>> may result in incorrectly calculated text widths
>> that can cause Display to print incorrect line lengths
>>
>> PLAY [Create new user account] 
>> **************************************************************************************************
>>
>> TASK [Gathering Facts] 
>> **********************************************************************************************************
>> ok: [vMX]
>> ok: [vMX_RE]
>> ok: [vQFX]
>>
>> TASK [junipernetworks.junos.junos_user] 
>> *****************************************************************************************
>> fatal: [vMX]: FAILED! => {"changed": false, "module_stderr": "", 
>> "module_stdout": "\n{\"failed\": true, \"msg\": \"Method not found\", 
>> \"invocation\": {\"module_args\": {\"name\": \"testusr\", \"role\": 
>> \"super-user\", \"state\": \"present\", \"purge\": false, \"active\": true, 
>> \"aggregate\": null, \"full_name\": null, \"encrypted_password\": null, 
>> \"sshkey\": null, \"provider\": null}}}\n\n{\"failed\": true, \"msg\": 
>> \"Method not found\", \"invocation\": {\"module_args\": {\"name\": 
>> \"testusr\", \"role\": \"super-user\", \"state\": \"present\", \"purge\": 
>> false, \"active\": true, \"aggregate\": null, \"full_name\": null, 
>> \"encrypted_password\": null, \"sshkey\": null, \"provider\": null}}}\n", 
>> "msg": "MODULE FAILURE\nSee stdout/stderr for the exact error", "rc": 1}
>> fatal: [vQFX]: FAILED! => {"changed": false, "module_stderr": "", 
>> "module_stdout": "\n{\"failed\": true, \"msg\": \"Method not found\", 
>> \"invocation\": {\"module_args\": {\"name\": \"testusr\", \"role\": 
>> \"super-user\", \"state\": \"present\", \"purge\": false, \"active\": true, 
>> \"aggregate\": null, \"full_name\": null, \"encrypted_password\": null, 
>> \"sshkey\": null, \"provider\": null}}}\n\n{\"failed\": true, \"msg\": 
>> \"Method not found\", \"invocation\": {\"module_args\": {\"name\": 
>> \"testusr\", \"role\": \"super-user\", \"state\": \"present\", \"purge\": 
>> false, \"active\": true, \"aggregate\": null, \"full_name\": null, 
>> \"encrypted_password\": null, \"sshkey\": null, \"provider\": null}}}\n", 
>> "msg": "MODULE FAILURE\nSee stdout/stderr for the exact error", "rc": 1}
>> fatal: [vMX_RE]: FAILED! => {"changed": false, "module_stderr": "", 
>> "module_stdout": "\n{\"failed\": true, \"msg\": \"Method not found\", 
>> \"invocation\": {\"module_args\": {\"name\": \"testusr\", \"role\": 
>> \"super-user\", \"state\": \"present\", \"purge\": false, \"active\": true, 
>> \"aggregate\": null, \"full_name\": null, \"encrypted_password\": null, 
>> \"sshkey\": null, \"provider\": null}}}\n\n{\"failed\": true, \"msg\": 
>> \"Method not found\", \"invocation\": {\"module_args\": {\"name\": 
>> \"testusr\", \"role\": \"super-user\", \"state\": \"present\", \"purge\": 
>> false, \"active\": true, \"aggregate\": null, \"full_name\": null, 
>> \"encrypted_password\": null, \"sshkey\": null, \"provider\": null}}}\n", 
>> "msg": "MODULE FAILURE\nSee stdout/stderr for the exact error", "rc": 1}
>>
>> Thanks,
>> Nish
>> On Wednesday, December 22, 2021 at 2:22:12 PM UTC-8 Felix Fontein wrote:
>>>
>>> Hi,
>>>
>>> > *[root@localhost ansible-content]# cat playbook-Create_User.yml----
>>> > name: Create new user account hosts: all #connection: local
>>> > junipernetworks.junos.junos_user: name: ansibleusr role:
>>> > super-user state: present*
>>>
>>> you need to use the `tasks:` keyword and move the actual task into
>>> there. This is not a valid playbook (with or without collections).
>>>
>>> Something like:
>>>
>>> - hosts: all
>>> tasks:
>>> - junipernetworks.junos.junos_user:
>>> name: ansibleusr
>>> role: super-user
>>> state: present
>>>
>>> Cheers,
>>> Felix
>>>
>> --
>> 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/f75a250a-0e40-464f-9b18-1256ea2d99b0n%40googlegroups.com.
>
> --
> 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/CAL8fbwM8-C%2BCYHwNR2J-Dh%3DOp6yyZjT3Mvr8JOWKGtf-TcHyfw%40mail.gmail.com.

-- 
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/CAOCN9rxgmJ4oxoF9CuK_zjD2Tn%3DQaYoVWDrRKMLbzguJ643%2BBg%40mail.gmail.com.

Reply via email to