Possible netd // zebra bug #1461
Description
Current Behavior
The test DHCP Router fails on one test system on the main branch:
Starting test 0112 DHCP Router (../case/dhcp/client_default_gw/test.py)
Test File: /home/alder/.ghmoon/kernelkit/infix/git/test/case/dhcp/client_default_gw/test.py
Test Cmdl: []
2026-03-30 14:53:28 # Starting (2026-03-30 14:53:28)
2026-03-30 14:53:28 # host: monza
2026-03-30 14:53:28 # mgmt: sw2p1
2026-03-30 14:53:28 # data: sw2p5
2026-03-30 14:53:28 # client: alder1
2026-03-30 14:53:28 # mgmt: x10
2026-03-30 14:53:28 # data: x9
2026-03-30 14:53:28 #
2026-03-30 14:53:28 # Waiting for DUTs to become reachable...
2026-03-30 14:53:29 # Probing alder1 on port sw2p1 for IPv6LL mgmt address ...
2026-03-30 14:53:29 # Testing using RESTCONF
2026-03-30 14:53:29 # YANG models downloaded.
2026-03-30 14:53:31 ok 1 - Initialize
2026-03-30 14:53:31 ok 2 - Set up DHCP server as 192.168.0.1, option 3: 192.168.0.254
udhcpd: started, v1.36.1
udhcpd: sending OFFER to 192.168.0.107
udhcpd: sending ACK to 192.168.0.107
udhcpd: received SIGTERM
2026-03-30 14:53:45 not ok 3 - Verify DHCP client has default route via 192.168.0.254
2026-03-30 14:53:45 # Exiting (2026-03-30 14:53:45)
2026-03-30 14:53:45 # Traceback (most recent call last):
2026-03-30 14:53:45 # File "/home/alder/.ghmoon/kernelkit/infix/git/test/case/dhcp/client_default_gw/test.py", line 45, in
2026-03-30 14:53:45 # until(lambda: route.ipv4_route_exist(client, "0.0.0.0/0", ROUTER))
2026-03-30 14:53:45 # File "/home/alder/.ghmoon/kernelkit/infix/git/test/infamy/util.py", line 55, in until
2026-03-30 14:53:45 # raise Exception("Expected condition did not materialize")
2026-03-30 14:53:45 # Exception: Expected condition did not materialize
2026-03-30 14:53:45 # 1..3
test error, no plan
See https://gist.github.com/ael-bot/273f89d1f1634476636a200519dc26a1
Expected Behavior
This test should never fail.
Steps To Reproduce
No response
Additional information
It is very likely that this fails due to the Frr upgrade and new netd service that's responsible for communicating DHCP client changes to Frr, which in turn is responsible for activating any route changes in the kernel via Zebra.