<feed xmlns='http://www.w3.org/2005/Atom'>
<title>vyos-1x.git/src/services/vyos-configd, branch rolling</title>
<subtitle>VyOS command definitions, scripts, and utilities (mirror of https://github.com/vyos/vyos-1x.git)
</subtitle>
<id>https://git.amelek.net/vyos/vyos-1x.git/atom?h=rolling</id>
<link rel='self' href='https://git.amelek.net/vyos/vyos-1x.git/atom?h=rolling'/>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-1x.git/'/>
<updated>2026-10-09T11:37:43+00:00</updated>
<entry>
<title>vpp: T9161: Fix smoketests failing on NICs capped at 1500 MTU</title>
<updated>2026-10-09T11:37:43+00:00</updated>
<author>
<name>Nataliia Solomko</name>
<email>natalirs1985@gmail.com</email>
</author>
<published>2026-10-09T11:19:11+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-1x.git/commit/?id=c254b0dca087083b77dea7dc3c8c3a797be7cf72'/>
<id>urn:sha1:c254b0dca087083b77dea7dc3c8c3a797be7cf72</id>
<content type='text'>
VPP now rejects an MTU above the NIC limit, but the CI NICs are capped
at 1500, so tests using MTU 2500 on eth1 failed. The rejected commit
also left a queued initial VPP dependency in the commit daemon, which
the next commit ran with the old config, so every following test failed
too. Pending initial dependents are now cleared before each script run
in vyos-configd and vyos-commitd, and the tests use MTUs that fit any
NIC.
</content>
</entry>
<entry>
<title>frrender: T9368: reconcile FRR after a DHCP lease without the commit socket</title>
<updated>2026-10-07T17:59:13+00:00</updated>
<author>
<name>Christian Breunig</name>
<email>christian@breunig.cc</email>
</author>
<published>2026-10-07T17:59:13+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-1x.git/commit/?id=c8d75f88f078c8c2c2a1f6a9a62c937424279d4b'/>
<id>urn:sha1:c8d75f88f078c8c2c2a1f6a9a62c937424279d4b</id>
<content type='text'>
Reconciling the FRR configuration after a DHCP lease event was requested from
the configuration daemon over the socket the commit pipeline uses. The daemon
serves one client at a time and assumes it is the running commit, so
the request either landed in the middle of the handshake which hands over the
configuration, or kept the daemon busy past the 10ms a commit waits for it.

Either way the commit fell back to running the conf-mode scripts directly.
Those never render FRR, only the daemon does, so the commit succeeded while FRR
kept the configuration rendered before it, until the next lease event.

A lease event now renders FRR in its own process, and a commit which could not
use the daemon renders FRR itself instead of skipping the reload. Both take the
same lock. A commit post-hook would remove the second case, for a full render
on every commit.
</content>
</entry>
<entry>
<title>T8482: reject commits referencing an incomplete policy object</title>
<updated>2026-08-18T17:23:11+00:00</updated>
<author>
<name>Christian Breunig</name>
<email>christian@breunig.cc</email>
</author>
<published>2026-08-18T13:47:10+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-1x.git/commit/?id=b58881fda8eba5b4a6d3479c4f6eb8c98efd8f4f'/>
<id>urn:sha1:b58881fda8eba5b4a6d3479c4f6eb8c98efd8f4f</id>
<content type='text'>
A verify() failure in one conf_mode script (e.g. "policy prefix-list")
did not stop vyos-configd/vyos-commitd from still pushing the shared
FRR configuration to vtysh once the last script in the same commit
batch happened to succeed on its own, since the render step only checked
that last script's own result. Track whether any earlier script in the
batch failed and gate the shared FRR render on it in both commit daemons.
</content>
</entry>
<entry>
<title>T9068: refactor vyos-configd with config manager</title>
<updated>2026-07-09T02:27:45+00:00</updated>
<author>
<name>John Estabrook</name>
<email>jestabro@vyos.io</email>
</author>
<published>2026-07-08T21:06:20+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-1x.git/commit/?id=b14a010b07de95f36e9d0d420ea7f74fa062ad39'/>
<id>urn:sha1:b14a010b07de95f36e9d0d420ea7f74fa062ad39</id>
<content type='text'>
</content>
</entry>
<entry>
<title>T5811: Make static dhcp-interface routes robust</title>
<updated>2025-10-21T16:57:40+00:00</updated>
<author>
<name>Kyrylo Yatsenko</name>
<email>hedrok@gmail.com</email>
</author>
<published>2025-10-17T10:58:01+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-1x.git/commit/?id=c4632bb6ad6c055fb7fe5a5c055354c6895ba8e5'/>
<id>urn:sha1:c4632bb6ad6c055fb7fe5a5c055354c6895ba8e5</id>
<content type='text'>
Solves the problem that vyos-configs in FRRender caches configuation and
DHCP changes are ignored.

* Add src/helpers/vyos-request-configd-update.py that requests vyos-configd
  to update FRR configuration.
* Make dhclient hooks use it instead of calling protocols_static.py
* Make FRRender cache not only configuration but also DHCP gateways so
  that is any of them changes, FRR configuration is updated
</content>
</entry>
<entry>
<title>T7946: log redirected stdout from FRRender</title>
<updated>2025-10-20T15:14:55+00:00</updated>
<author>
<name>John Estabrook</name>
<email>jestabro@vyos.io</email>
</author>
<published>2025-10-20T14:01:43+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-1x.git/commit/?id=40c95fe290b0d2c546756d5bf3caee0435df7512'/>
<id>urn:sha1:40c95fe290b0d2c546756d5bf3caee0435df7512</id>
<content type='text'>
After T7855, logging of stdout from FRRender was dropped. Explicity log
redirected stdout in vyos-configd/commitd; restore parity of logging
between the two daemons.
</content>
</entry>
<entry>
<title>T7855: vyos-configd redirect stdout and catch exceptions on frr render</title>
<updated>2025-09-23T20:41:20+00:00</updated>
<author>
<name>John Estabrook</name>
<email>jestabro@vyos.io</email>
</author>
<published>2025-09-22T01:34:17+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-1x.git/commit/?id=025c700837fe760748d57c8b93c58adfd96f1bcf'/>
<id>urn:sha1:025c700837fe760748d57c8b93c58adfd96f1bcf</id>
<content type='text'>
</content>
</entry>
<entry>
<title>T7591: remove copyright years from source files</title>
<updated>2025-06-28T21:16:52+00:00</updated>
<author>
<name>Christian Breunig</name>
<email>christian@breunig.cc</email>
</author>
<published>2025-06-28T18:51:21+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-1x.git/commit/?id=1478516ae437f19ebeb7d6ff9b83dd74f8e76758'/>
<id>urn:sha1:1478516ae437f19ebeb7d6ff9b83dd74f8e76758</id>
<content type='text'>
The legal team says years are not necessary so we can go ahead with it, since
it will simplify backporting.

Automatically removed using: git ls-files | grep -v libvyosconfig | xargs sed -i -E \
's/^# Copyright (19|20)[0-9]{2}(-[0-9]{4})? VyOS maintainers.*/# Copyright VyOS maintainers and contributors &lt;maintainers@vyos.io&gt;/g'

In addition we will error-out during "make" if someone re-adds a legacy
copyright notice
</content>
</entry>
<entry>
<title>configd: T7488: allow distinction of first-order error verify vs apply</title>
<updated>2025-06-10T23:12:48+00:00</updated>
<author>
<name>John Estabrook</name>
<email>jestabro@vyos.io</email>
</author>
<published>2025-05-23T15:31:18+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-1x.git/commit/?id=c82b2b836b01c285576cc98ecf2b99ff3d8838ef'/>
<id>urn:sha1:c82b2b836b01c285576cc98ecf2b99ff3d8838ef</id>
<content type='text'>
Leave hint if vyos-configd encounters an error in the generate/apply
stages: this only detects 'first-order' differences, meaning those
originating from the called config mode script, and not its
dependencies. This is useful for supporting automatic rollback for
certain cases of apply stage error.
</content>
</entry>
<entry>
<title>configd: T7119: fix misleading debug messages</title>
<updated>2025-01-31T18:06:46+00:00</updated>
<author>
<name>John Estabrook</name>
<email>jestabro@vyos.io</email>
</author>
<published>2025-01-31T17:31:26+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-1x.git/commit/?id=213440666e0d2379ed3e686e0e66ec535d0c4d45'/>
<id>urn:sha1:213440666e0d2379ed3e686e0e66ec535d0c4d45</id>
<content type='text'>
An artifact of T6899 included a report of 'error_code 1' on success: for
consistency with shim error codes 1 == SUCCESS, however, the debug
message is misleading and is here corrected.
</content>
</entry>
</feed>
