[dhcp_relay] Add dhcp6relay runtime reconfiguration tests - #25589
[dhcp_relay] Add dhcp6relay runtime reconfiguration tests#25589AnantKishorSharma wants to merge 1 commit into
Conversation
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
6f012d7 to
b71c612
Compare
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azpw retry |
|
Retrying failed(or canceled) jobs... |
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
CI status — expected red until the companion PRs are in the imageThe These tests exercise the SONiC-native
|
b71c612 to
f3a1a83
Compare
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Add sonic-mgmt tests that dhcp6relay applies configuration at runtime without restarting the dhcp_relay container: - starts when no dhcpv6_servers are configured - adds a relay instance when a VLAN gets an IPv6 address at runtime, and removes it when that address is removed - applies dhcpv6_server changes in place (PID unchanged, no "need restart container" log) Signed-off-by: Anant Kishor Sharma <anant.kishor-sharma@hpe.com>
f3a1a83 to
6cd746c
Compare
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azpw run |
|
Retrying failed(or canceled) jobs... |
|
Retrying failed(or canceled) stages in build 1163914: ✅Stage Test:
|
|
/azpw retry |
|
Retrying failed(or canceled) jobs... |
|
Retrying failed(or canceled) stages in build 1163914: ✅Stage Test:
|
3 participants
Why I did it
Add functional coverage for the SONiC-native
dhcp6relayapplyingDHCP_RELAYconfiguration at runtime, without adhcp_relaycontainer restart (sonic-net/sonic-dhcp-relay#116).How I did it
tests/dhcp_relay/test_dhcpv6_relay_runtime_config.py(topologyt0/m0/mx/t0-2vlans,device_typevs) — 4 tests driven entirely through CONFIG_DB:test_dhcp6relay_starts_without_dhcpv6_serverstest_dhcp6relay_runtime_ipv6_added_after_starttest_dhcp6relay_runtime_server_change_no_restarttest_dhcp6relay_runtime_relay_removed_no_restartEach asserts the relay applies the change at runtime (the
Add/Update/Remove relay config ... at runtimesyslog), the process PID is unchanged, and the legacyneed restart container to take effectlog is not emitted.How to verify it
On a qfx5200
t0testbed with the dhcp6relay change deployed:Companion PRs: sonic-net/sonic-dhcp-relay#116 (core) · sonic-net/sonic-buildimage sonic-net/sonic-buildimage#28042 · sonic-net/SONiC sonic-net/SONiC#2402 (HLD)
CI note —
impacted-area-kvmtestfailures are expected hereThese tests assert the runtime-reconfig behavior from sonic-net/sonic-dhcp-relay#116,
which isn't in the
vsimage yet (baselinedhcp6relaystill restarts and emitsneed restart container to take effect), so the*_no_restartcases correctly fail.