sendnrw/netbird
2
0
Fork 0
mirror of https://github.com/netbirdio/netbird.git synced 2026-10-13 00:49:07 +02:00
Code Issues Packages Projects Releases Wiki Activity

Force eager peer connections in the agent-network e2e harness

Browse Source 
The nightly agent-network e2e has been red for ~6 days: every scenario
that calls WaitProxyPeer times out with 'client did not see the proxy
peer'. The proxy's overlay peer comes up fine, but the client now puts
it into the lazy connection manager (server-driven feature flag), so no
connection is dialed until traffic flows — and WaitProxyPeer polls
'netbird status' for a Connected peer before sending any traffic.

Set NB_LAZY_CONN=false on the harness client and proxy containers so
the tunnel dials eagerly and status reflects it, restoring the
harness's readiness signal.
This commit is contained in:
Claude
2026-07-21 10:03:00 +00:00
parent e7412361c7
commit a79363d801
2 changed files with 9 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
e2e/harness/proxy.go
+4
View File
@@ -77,6 +77,10 @@ func StartProxy(ctx context.Context, c *Combined, proxyToken string) (*Proxy, er
// Management is plain HTTP in-cluster, so allow the proxy token to
// ride a non-TLS gRPC connection.
"NB_PROXY_ALLOW_INSECURE": "true",
// Keep the embedded overlay peer eager (see the client env note):
// lazy connections leave peers unconnected until traffic, which
// starves the harness's WaitProxyPeer.
"NB_LAZY_CONN": "false",
// The combined server multiplexes the relay over WebSocket on :8080
// (no QUIC listener). The proxy's embedded relay client defaults to
// QUIC, which fails here and flaps the relay link, churning the