Skip to content

Conversation

Ruchip16
Copy link

@Ruchip16 Ruchip16 commented Oct 5, 2025

  1. [WARNING]: errors were encountered during the plugin load for junipernetworks.junos.junos_command: ["'NoneType' object has no attribute 'get'"]

Cause: A bad/partial plugin routing in a collection that Ansible is loading from your local workspace (likely junipernetworks/junos/meta/runtime.yml). An entry in plugin_routing is null/missing keys, so the loader expects a dict and hits .get() on None.

This PR fixes that, if you remove the empty action key it removes the warning as its not necessary.

fixes: #772

@chidanandpujar
Copy link
Collaborator

chidanandpujar commented Oct 7, 2025

Hi @Ruchip16,
Thanks, this will be fixed as part of - ansible-collections/junipernetworks.junos#574

@Ruchip16
Copy link
Author

Ruchip16 commented Oct 8, 2025

hi @chidanandpujar why are we doing the changes in ansible-collections/junipernetworks.junos#574, i dont think its needed, only my suggested change to fix those warnings is needed here : #777

@chidanandpujar
Copy link
Collaborator

hi @chidanandpujar why are we doing the changes in ansible-collections/junipernetworks.junos#574, i dont think its needed, only my suggested change to fix those warnings is needed here : #777

Hi @Ruchip16 ,
This was already discussed with Rohit, to support redirection to juniper.device collection path for Redhat ansible collection users, so that existing Redhat customer playbooks continue to work with redirection support.

Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants