Today I was trying to write a playbook to push config to Arista devices. <\/p>\n\n\n\n
Initially I wanted to use napalm module to push the config (as I have done with nornir) but it seems the napalm-ansible module requires napalm3 and netmiko3 and that breaks my nornir2.4 ( that requires napalm<3) So I uninstalled napalm-ansible and restored the other packages. Good thing i chekced the version before hand.<\/p>\n\n\n\n
$ python -m pip list | grep -E 'nornir|napalm|netmiko|ansible'\nansible 2.9.10\nnapalm 2.5.0\nnetmiko 2.4.2\nnornir 2.4.0<\/pre>\n\n\n\nSo I had to check the eos_config<\/a> module. I think the napalm-ansible module is more powerful as it uses diff and sessions provided by Arista. As far as I can see, there is no option to say to the module to just make a dry run.<\/p>\n\n\n\n
At the end I managed to put everything together but the eos_config was failing:<\/p>\n\n\n\n
TASK [11- push config]\ntask path: xxx\/testdir2\/ceos-testing\/ansible\/playbooks\/gen-config.yaml:60\nfatal: [r1]: FAILED! => {\n\"changed\": false,\n\"msg\": \"path specified in src not found\"\n}<\/pre>\n\n\n\nThe funny thing is all other tasks that needed to use templates were using the same path and were fine:<\/p>\n\n\n\n
- name: 10- merge all configs in one file\n assemble:\n src: \"CFGS\/{{ inventory_hostname }}\/\" \n dest: \"CFGS\/{{ inventory_hostname }}-full.txt\"\n\n- name: 11- push config\n debugger: on_failed\n eos_config:\n #src: \"{{playbook_dir}}\/..\/CFGS\/{{ inventory_hostname }}-full.txt\"\n src: \"..\/CFGS\/{{ inventory_hostname }}-full.txt\"\n backup: yes<\/code><\/pre>\n\n\n\nSo I had to find out where that task was looking for the file. It seems “assemble<\/em>“, “template<\/em>” and “file<\/em>” tasks use as pwd<\/strong> where I am calling the script (xxx\/testdir2\/ceos-testing\/ansible<\/em>). But “eos_config<\/em>” is using where the playbook is (xxx\/testdir2\/ceos-testing\/ansible\/playbook<\/em>) based on my running command “…\/ansible master$ ansible-playbook playbooks\/gen-config.yaml<\/em>“.<\/p>\n\n\n\n
So I was searching for some help and I found the playbook path<\/a> and ansible search paths<\/a>. So now I needed to verify that. I found some ansible debugger<\/a> and examples<\/a> that were really useful!<\/p>\n\n\n\n
So I used “debugger: on_failed” for my task 11. And could see the path:<\/p>\n\n\n\n
TASK [11- push config]\ntask path: \/home\/tomas\/storage\/technology\/arista\/testdir2\/ceos-testing\/ansible\/playbooks\/gen-config.yaml:60\nfatal: [r1]: FAILED! => {\n\"changed\": false,\n\"msg\": \"path specified in src not found\"\n}\n[r1] TASK: 11- push config (debug)> p task.args<\/strong>\n{'backup': True,\n'src<\/em>': '\/home\/tomas\/storage\/technology\/arista\/testdir2\/ceos-testing\/ansible\/playbooks\/CFGS\/r1-full.txt<\/em>'}\n[r1] TASK: 11- push config (debug)> quit<\/strong>\nUser interrupted execution<\/pre>\n\n\n\nSo it is clear it was looking at the playbook dir. <\/p>\n\n\n\n
So after fixing the path, I realised that I didn’t want to run everything and wanted to use tags<\/a> so only the last part was executed.<\/p>\n\n\n\n
\/ansible master$ cat playbooks\/gen-config.yaml\n...\n- name: 12- display result <\/code>\ndebug: msg: \"Backup file is {{ load_config.shortname }} and result is: {{ load_config }}\" <\/code>\ntags<\/strong>: push_config<\/strong><\/code>\n...\n\n\/ansible master$ ansible-playbook playbooks\/gen-config.yaml --limit=\"r1\" -vvv --tags<\/strong> \"push_config\"<\/pre>\n\n\n\nOne more thing, the output of ansible when you have dictionaries, it is not great. I checked this link<\/a> and it is good for failures and with -vvvv. But for green outputs still not great:<\/p>\n\n\n\n
TASK [12- - display result] *\ntask path: \/home\/tomas\/storage\/technology\/arista\/testdir2\/ceos-testing\/ansible\/playbooks\/gen-config.yaml:61\nok: [r1] =>\nmsg: 'Backup file is \/home\/tomas\/storage\/technology\/arista\/testdir2\/ceos-testing\/ansible\/playbooks\/backup\/r1_config and result is: {''changed'': True, ''commands'': [''interface Ethernet1'', ''no shutdown'', ''interface Ethernet2'', ''no shutdown'', ''router bgp 100'', ''neighbor AS100-CORE password mpls-sr''], ''updates'': [''interface Ethernet1'', ''no shutdown'', ''interface Ethernet2'', ''no shutdown'', ''router bgp 100'', ''neighbor AS100-CORE password mpls-sr''], ''session'': ''ansible_1594920727'', ''backup_path'': ''\/home\/tomas\/storage\/technology\/arista\/testdir2\/ceos-testing\/ansible\/playbooks\/backup\/r1_config.2020-07-16@18:32:07'', ''date'': ''2020-07-16'', ''time'': ''18:32:07'', ''shortname'': ''\/home\/tomas\/storage\/technology\/arista\/testdir2\/ceos-testing\/ansible\/playbooks\/backup\/r1_config'', ''filename'': ''r1_config.2020-07-16@18:32:07'', ''failed'': False}'\nMETA: ran handlers\nMETA: ran handlers\nPLAY RECAP\nr1 : ok=3 changed=1 unreachable=0 failed=0 skipped=0 rescued=0 ignored=0\n(testdir2) go:1.12.5|py:3.7.3|tomas@athens:~\/storage\/technology\/arista\/testdir2\/ceos-testing\/ansible master$<\/pre>\n","protected":false},"excerpt":{"rendered":"Today I was trying to write a playbook to push config to Arista devices. Initially I wanted to use napalm module to push the config (as I have done with nornir) but it seems the napalm-ansible module requires napalm3 and netmiko3 and that breaks my nornir2.4 ( that requires napalm<3) So I uninstalled napalm-ansible and … Continue reading “Ansible Troubleshooting 2”<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[21],"tags":[],"class_list":["post-302","post","type-post","status-publish","format-standard","hentry","category-automation"],"_links":{"self":[{"href":"https:\/\/blog.thomarite.uk\/index.php\/wp-json\/wp\/v2\/posts\/302","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blog.thomarite.uk\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.thomarite.uk\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.thomarite.uk\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.thomarite.uk\/index.php\/wp-json\/wp\/v2\/comments?post=302"}],"version-history":[{"count":2,"href":"https:\/\/blog.thomarite.uk\/index.php\/wp-json\/wp\/v2\/posts\/302\/revisions"}],"predecessor-version":[{"id":313,"href":"https:\/\/blog.thomarite.uk\/index.php\/wp-json\/wp\/v2\/posts\/302\/revisions\/313"}],"wp:attachment":[{"href":"https:\/\/blog.thomarite.uk\/index.php\/wp-json\/wp\/v2\/media?parent=302"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.thomarite.uk\/index.php\/wp-json\/wp\/v2\/categories?post=302"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.thomarite.uk\/index.php\/wp-json\/wp\/v2\/tags?post=302"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}