Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

napalm-vyos does not clean up candidate_running or backup_running #46

Open
yzguy opened this issue Jun 11, 2023 · 0 comments · Fixed by routedbits/napalm-vyos#2
Open

Comments

@yzguy
Copy link

yzguy commented Jun 11, 2023

So one issue I experienced is that I applied a config from napalm-vyos with the vyos user which was to add my personal user. This works fine.

However on the next run if I try to do a diff/commit with my personal user I get an error

fatal: [router1]: FAILED! => changed=false 
  msg: |-
    cannot load config: scp: /var/tmp/candidate_running.conf: Permission denied

This seems to be because the /var/tmp/candidate_running.conf file is left around from previous runs and has 644 permissions, only allowing the vyos user to write to it. This wouldn't become an issue if these files were cleaned up after the operation(s) are finished, which it seems the code as of now does not do that.

vyos@dev:~$ ls -la /var/tmp
total 20
drwxrwxrwt  6 root  root   180 Jun 11 16:50 .
drwxr-xr-x  1 root  
-rwxr-xr-x  1 vyos  users 1896 Jun 11 16:48 backup_running.conf
-rw-r--r--  1 vyos  users 1784 Jun 11 16:48 candidate_running.conf
-rw-r--r--  1 yzguy users  182 Jun 11 16:50 test.sh
@yzguy yzguy changed the title napalm-vyos does not clean up canidate_running or backup_running napalm-vyos does not clean up candidate_running or backup_running Jun 21, 2023
@yzguy yzguy reopened this Jun 21, 2023
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 a pull request may close this issue.

1 participant