ansible_network_working_group
LOGS
16:01:33 <Qalthos> #startmeeting Ansible Network Working Group
16:01:33 <zodbot> Meeting started Wed Jul  8 16:01:33 2020 UTC.
16:01:33 <zodbot> This meeting is logged and archived in a public location.
16:01:33 <zodbot> The chair is Qalthos. Information about MeetBot at http://wiki.debian.org/MeetBot.
16:01:33 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
16:01:33 <zodbot> The meeting name has been set to 'ansible_network_working_group'
16:01:43 <Qalthos> #chair pabelanger
16:01:44 <zodbot> Current chairs: Qalthos pabelanger
16:02:08 <Qalthos> #link https://github.com/ansible/community/labels/network is where the agenda always lives
16:02:15 <Qalthos> #topic Core Updates
16:03:13 <Qalthos> #info Collection repositories are in the process of moving from default branch "master" to "main"
16:04:15 <Qalthos> #info this is a somewhat complicated process as we have tooling that needs to update as we do this, but most repos are migrated, and the remainder should be along soon
16:05:29 <Qalthos> #info This might result in some dead links in, for example. docs... please bear with us and report anything if you notice orphaned references
16:10:56 <Qalthos> #info Virtual Contributor's Summit happened on Monday, covered a variety of topics including collections and communities going forward
16:11:28 <Qalthos> I think there should be a video going out soon, I'll try to link here if I can find it
16:13:04 <Qalthos> #info We're starting through tasks for the next release of our supported collections
16:13:15 <Qalthos> #link https://github.com/orgs/ansible-collections/projects/3 to see what we're working on
16:13:43 <Qalthos> I think that's everything this week.
16:13:47 <Qalthos> #topic Open Floor
16:14:15 <Qalthos> Does anyone have anything to bring up this week?
16:22:10 <jge> I have this very simple task: https://bpa.st/3EUA but I'm getting "module_stderr": "/bin/sh: sudo: not found\n", "module_stdout"
16:22:49 <jge> why is it trying to sudo when I specifically pass the command to the module and connection is set to NetConf??
16:23:09 <jge> there's something very basic I must be missing here.
16:28:15 <Qalthos> Hmm, I think that's a usually symptom of become being set without the enable plugin being changed
16:28:25 <Qalthos> But I'm not sure if that's what's going on here
16:29:03 <Qalthos> Do you have actual logs you can share?
16:34:13 <Qalthos> (alternately, if you set `ansible_become_method: enable` and it goes away, then you probably have become set somewhere and you don't need it)
16:36:37 <jge> Qalthos: does this help? https://bpa.st/HCRA
16:42:17 <jge> ok so adding ansible_become_method: enable to my group_vars made it go away.. I still don't understand why that was needed, where in the module's documentation points to having this set in the examples show? https://docs.ansible.com/ansible/latest/modules/junos_command_module.html#junos-command-module
16:42:30 <Qalthos> Somewhat. It does show that you're running this with become, and you probably shouldn't be.
16:42:50 <Qalthos> https://docs.ansible.com/ansible/latest/user_guide/become.html#become-and-network-automation is the page that deals with become and network modules
16:43:11 <jge> I have this in a role, I don't know where else I could be running this with become..
16:45:13 <Qalthos> I really couldn't say. If you're not calling ansible with `-b` and it's not set in your inventory then maybe the role is setting it somewhere for some reason?
16:45:56 <Qalthos> Ah, okay, you can also set it in ansible.cfg
16:46:22 <jge> let me check that
16:47:24 <Qalthos> `ansible-config dump --only-changed` helps for checking config
16:47:40 <jge> thank u
16:49:01 <jge> yikes, it's setting it :(
16:49:10 <Qalthos> All right, I'll still be here, but it doesn't look like there's anything else for the meeting so
16:49:13 <Qalthos> #endmeeting