2026-05-23 19:49:49 # Starting (2026-05-23 19:49:49)
2026-05-23 19:49:49 # host: monza
2026-05-23 19:49:49 # mgmt: sw2p1
2026-05-23 19:49:49 # data: sw2p5
2026-05-23 19:49:49 # client: alder1
2026-05-23 19:49:49 # mgmt: x10
2026-05-23 19:49:49 # data: x9
2026-05-23 19:49:49 #
2026-05-23 19:49:49 # Waiting for DUTs to become reachable...
2026-05-23 19:49:49 # Probing alder1 on port sw2p1 for IPv6LL mgmt address ...
2026-05-23 19:49:49 # Testing using NETCONF
2026-05-23 19:49:49 # Connecting to mgmt IP fe80::e002:a5ff:fe06:70a%sw2p1:830 ...
2026-05-23 19:49:49 # YANG models downloaded.
2026-05-23 19:49:51 ok 1 - Setting up canary route, 20.0.0.0/24 via 192.168.0.2
2026-05-23 19:49:52 ok 2 - Enabling DHCP client, allow option 3 and 121
2026-05-23 19:49:52 # Start DHCP server 192.168.0.254 with option 3 and 121
2026-05-23 19:49:52 # Verify client use classless routes, option 121
2026-05-23 19:50:05 not ok 3 - Verify client has route 10.0.0.0/24 via 192.168.0.254 (option 121)
2026-05-23 19:50:05 # Exiting (2026-05-23 19:50:05)
2026-05-23 19:50:05 # Traceback (most recent call last):
2026-05-23 19:50:05 # File "/home/alder/.ghmoon/kernelkit/infix/git/test/case/dhcp/client_routes/test.py", line 84, in <module>
2026-05-23 19:50:05 # until(lambda: route.ipv4_route_exist(client, PREFIX, ROUTER))
2026-05-23 19:50:05 # File "/home/alder/.ghmoon/kernelkit/infix/git/test/infamy/util.py", line 55, in until
2026-05-23 19:50:05 # raise Exception("Expected condition did not materialize")
2026-05-23 19:50:05 # Exception: Expected condition did not materialize
2026-05-23 19:50:05 # 1..3
I cannot back this claim up, but I believe I've seen this more often on the Alder test system than any other.
Current Behavior
Sometimes test/case/dhcp/client_routes/test.py fails:
Expected Behavior
PASS
Steps To Reproduce
No response
Additional information
I cannot back this claim up, but I believe I've seen this more often on the Alder test system than any other.