Age | Commit message (Collapse) | Author |
|
T5660: Remove redundant calls to config dependency scripts
|
|
related task: T5660: add marker for last element of priority queues
(cherry picked from commit 5183b6fd34e4a9a5443406e801ec70139e68c471)
|
|
(cherry picked from commit 2411564dead4a27d155a13973e8fd4b438546dce)
|
|
dhcp: T5846: Have separate DUID formatter hint (backport #71)
|
|
Have separate custom DUID formatter hint for config shell.
(cherry picked from commit 18bdce6a6eed71866397c793fb2dafb92c890565)
|
|
T5249: Add node rollback-soft (backport #69)
|
|
```
vyos@r4# rollback-soft
Possible completions:
<N> Rollback to revision N
```
(cherry picked from commit 6ddafd315aade19f62903c5b749309e54e872ea9)
|
|
save-config: T4292: use vyos-save-config.py
|
|
|
|
|
|
T5291: vyatta-cfg-cmd-wrapper missing ${vyos_libexec_dir} variable
|
|
|
|
|
|
T775: Add postcommit-hooks in run directory
|
|
Use /run/scripts/commit/post-hooks.d directory for scripts generated
by "set service config-sync"
|
|
|
|
In file: /opt/vyatta/sbin/vyatta-cfg-cmd-wrapper
Commit 9e74ad7 changed the vyos-load-config.py script directory prefix to use ${vyos_libexec_dir}. However, the ${vyos_libexec_dir} variable is not exported at the start of the wrapper script.
When executing the load command over an SSH session it tries to execute the vyos-load-config.py script from root, and not /usr/libexec/vyos where the script resides
$ /opt/scripts/vyos/reset-router-config.pl --debug
[--] Resetting VyOS router configuration...
[??] Connection vyos:vyos@10.35.22.1 established successfully
[??] Command : /opt/vyatta/sbin/vyatta-cfg-cmd-wrapper begin
[??] Command : /opt/vyatta/sbin/vyatta-cfg-cmd-wrapper load config.boot.sauron.master
/opt/vyatta/sbin/vyatta-cfg-cmd-wrapper: line 84: /vyos-load-config.py: No such file or directory
[??] Error running command: /opt/vyatta/sbin/vyatta-cfg-cmd-wrapper load config.boot.sauron.master
[??] child exited with code 127
[??] Command : /opt/vyatta/sbin/vyatta-cfg-cmd-wrapper commit
[??] Command : /opt/vyatta/sbin/vyatta-cfg-cmd-wrapper end
|
|
|
|
Commit 4bbb382 ("startup: T5239: ensure system hostname is set before FRR
starts") removed /etc/hostname but it cared about exit codes - always
remove the file even if it does not exist (--force)
|
|
|
|
Always clean our mess before re-adding it. This is required in /etc when
a user does a change but does not save the config - all his changes
should be reverted on reboot.
|
|
|
|
|
|
|
|
|
|
sempervictus/bug/T5053-cant_disable_service_after_removal
T5053 - Move postrm service hook to prerm
|
|
T671: remove unused executables
|
|
|
|
loadkey: T3506: Remove (what remains of) loadkey
|
|
|
|
|
|
debian: T5003: Fixes for GCC in Debian 12 "Bookworm"
|
|
Fixes compile error: void operator delete(void*, std::size_t)' called on pointer returned from a mismatched allocation function
|
|
commit: T4990: call sync after the commit completes
|
|
|
|
config-mgmt: T4942: use vyos-1x config-mgmt scripts
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
firewall: T2199: Use data file instead of conf script
|
|
|
|
cstore: T4664: add validation: no whitespace in tag node value names
|
|
|
|
T4607: Fallthrough to simple stream copy when Boost's copy_file fails
|
|
Kernel 5.15, and probably newer, present an EXEDEV error when the
vyatta-cfg code tries to boost::filesystem::copy_file on UnionFS
FUSE mounts. This completely breaks operation on newer kernels, and
is therefore a blocker to the rest of the project moving on to new
Linux LTS versions.
Boost is complex and fraught, this code behaves inconsistently in
verious operating environments, and can be a nightmare to debug.
Handle the concerns above using binary streaming in C++ to copy the
source to the destination if an exception occurs during the
existing Boost copy_file operation.
Testing:
Built ISO (cloud target), packer install, booted in OpenStack on
KVM, booted in AWS on Xen, verified configurations are committed in
both cases and that error logs are being generated to inform users
about the fall-through being utilized to write-out configurations.
Notes:
Logging may be dropped to avoid flooding storage on often-updated
systems. It is left in-place to aid developers in debugging the root
concern underpinning Boot breakage (which may impact other areas of
the code).
|
|
|