The file sent on commits are /opt/vyatta/etc/config/archive/config.boot and has different contents from the running config after new configurations is committed.
Description
Description
Details
Details
- Version
- 1.4.3
- Is it a breaking change?
- Unspecified (possibly destroys the router)
- Issue type
- Bug (incorrect behavior)
Event Timeline
Comment Actions
@seriv I am unable to reproduce on 1.4.3; for example:
vyos@vyos# run show version Version: VyOS 1.4.3 Release train: sagitta Release flavor: generic ... Architecture: x86_64 Boot via: installed image System type: KVM guest
vyos@vyos# show system config-management
commit-archive {
location scp://bobo@192.168.1.9/home/bobo/archive
}
commit-revisions 100
[edit]vyos@vyos# set service https api [edit] vyos@vyos# set service https api keys id some_id key some_key [edit] vyos@vyos# commit WARNING: No certificate specified, using build-in self-signed certificates. Do not use them in a production environment! Archiving config... scp://192.168.1.9/home/bobo/archive [edit]
(make a local copy of running config for comparison:)
vyos@vyos# save ./running.config [edit]
(explicit comparison)
vyos@vyos# diff ./running.config <(ssh bobo@192.168.1.9 'ls -t archive|head -n 1 | xargs -I {} cat archive/{}')
[edit]
vyos@vyos#(comparison with archived previous config)
vyos@vyos# diff ./running.config <(ssh bobo@192.168.1.9 'ls -t archive|head -n 2 |tail -n 1| xargs -I {} cat archive/{}')
19,27d18
< https {
< api {
< keys {
< id some_id {
< key "some_key"
< }
< }
< }
< }
[edit]
vyos@vyos#If you can provide further details that will allow us to reproduce, we can investigate from there. Thanks.