*Hey guys, I found the solution-*

The main issue was "junipernetworks.junos.junos_user" is created by core 
Ansible team and not maintained by Juniper team members. Whereas 
"juniper.device" is created and maintained by Juniper team members which 
takes API as ansible_connection=juniper.device.pyez . But that won't work 
on junipernetworks.junos.junos_user.

So the fix is to add following lines in inventory/host file.

*ansible_connection=ansible.netcommon.netconfansible_network_os=junipernetworks.junos.junos*

Thanks to everyone who took the time to help.
Solved :)
On Wednesday, January 5, 2022 at 12:21:17 PM UTC-8 nishant shah wrote:

> I think it is actually finding the right collection but somehow the 
> playbook is not running. Maybe the playbook I have is not right? Do you 
> have a link to a doc to troubleshoot  using the ANSIBLE_DEBUG environment 
> variable?
>
> *It can see the ansible-doc for that specific collection which I am trying 
> to use-*
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> *[root@ansiblectrl ansible-content]# ansible-doc-2.7 
> junipernetworks.junos.junos_user> JUNOS_USER   
>  
> (/root/.ansible/collections/ansible_collections/junipernetworks/junos/plugins/modules/junos_user.py)
>   
>       This module manages locally configured user accounts on remote 
> network devices running the JUNOS operating system.        It provides a 
> set of arguments for creating, removing and updating locally defined 
> accounts  * This module is maintained by The Ansible CommunityOPTIONS (= is 
> mandatory):- active        Specifies whether or not the configuration is 
> active or deactivated        [Default: True]        type: bool- aggregate  
>       The `aggregate' argument defines a list of users to be configured on 
> the remote device.  The list of users will be        compared against the 
> current users and only changes will be added or removed from the device 
> configuration.  This        argument is mutually exclusive with the name 
> argument.        (Aliases: users, collection)[Default: (null)]        
> elements: dict        suboptions:          active:            description:  
>           - Specifies whether or not the configuration is active or 
> deactivated            type: bool          encrypted_password:            
> description:            - The `encrypted_password' argument set already 
> hashed password for the user              account on the remote system.    
>         type: str          full_name:            description:            - 
> The `full_name' argument provides the full name of the user account to be 
> created              on the remote device.  This argument accepts any text 
> string value.            type: str          name:            description:  
>           - The `name' argument defines the username of the user to be 
> created on the system.  This              argument must follow appropriate 
> usernaming conventions for the target device              running JUNOS. 
>  This argument is mutually exclusive with the `aggregate' argument.        
>     required: true            type: str          purge:            default: 
> false            description:            - The `purge' argument instructs 
> the module to consider the users definition              absolute.  It will 
> remove any previously configured users on the device with              the 
> exception of the current defined set of ag*
>
> *Here is my Playbook that I am trying to run-*
>
>
>
> *[root@ansiblectrl ansible-content]# cat playbook-CreateUsers.yml---*
>
> *- name: create new user account  hosts: all*
>
>
>
>
>
>
>
>
>
> *  collections:    - junipernetworks.junos    - juniper.device  tasks:    
> - junipernetworks.junos.junos_user:        name: testuser        role: 
> super-user        state: present*
> On Tuesday, January 4, 2022 at 5:26:44 AM UTC-8 [email protected] wrote:
>
>>
>> Perhaps I was unclear but from the look of it, you don't have an issue 
>> finding the collection/module but you have an issue *within* the module 
>> itself. You could try to get some more information using the ANSIBLE_DEBUG 
>> environment variable, else I fear you'll have to debug the module.
>> On Monday 3 January 2022 at 20:56:47 UTC+1 [email protected] wrote:
>>
>>> Yes, using pip and ansible-galaxy collection.
>>>
>>>
>>>
>>>
>>> *[root@localhost ansible-content]# ansible-galaxy collection list | grep 
>>> junijunipernetworks.junos         2.8.0juniper.device       
>>>  1.0.1junipernetworks.junos 2.8.0*
>>>
>>> On Monday, January 3, 2022 at 10:52:42 AM UTC-8 [email protected] wrote:
>>>
>>>> On Mon, Jan 3, 2022 at 1:09 PM nishant shah <[email protected]> 
>>>> wrote: 
>>>> > 
>>>> > Hi, 
>>>> > 
>>>> > Yeah, I am using netconf over the SSH. I am able to update 
>>>> configuration on Juniper devices using roles. But somehow the Ansible 
>>>> can't 
>>>> find the collection althought it is installed. I am trying to using 
>>>> collections over roles because collections has more varieties. 
>>>>
>>>> Installed *where* ? How did you install it? With the "pip install" 
>>>> command as the root user? 
>>>>
>>>> Nico Kadel-Garcia 
>>>>
>>>

-- 
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/376ca945-3746-4725-8eca-ee4ce2912039n%40googlegroups.com.

Reply via email to