ci: cdrouter: flush DNS relay cache on loopback instance as well

Since the unbound upstep from 1.22 to 1.24.1 (commit d453d848c0), DNS
resolution now also uses a loopback unbound instance. The existing DUT
init script only flushed the "lan" DNS relay cache, causing stale
negative DNS entries on the "lo" instance to persist. This led to USP
agent (obuspa) STOMP connection failures during CDRouter-Wireless tests,
as controller.cdroutertest.com could not be resolved.

Flush the "lo" DNS relay cache before "lan" to ensure both instances
have clean state before CDRouter tests start.

Fixes: PPW-1629
Signed-off-by: Petr Štetiar <petr.stetiar@prplfoundation.org>
This commit is contained in:
Petr Štetiar 2026-03-09 18:05:27 +00:00
parent 44b2900f69
commit a5d9c5ce2d
No known key found for this signature in database
GPG Key ID: 58EE120F30CC02D3

View File

@ -1,4 +1,5 @@
#!/bin/bash
ssh "root@$TARGET_LAN_IP" "ubus -t 180 wait_for DNS.Relay.Config.1"
ssh "root@$TARGET_LAN_IP" "ba-cli 'DNS.Relay.Config.[Alias==\"lo\"].FlushCache()'"
ssh "root@$TARGET_LAN_IP" "ba-cli 'DNS.Relay.Config.[Alias==\"lan\"].FlushCache()'"