Skip to content

e2e: tolerate multiple tunnel statuses in all-devices unicast QA test#3976

Open
thijsvanemmerik wants to merge 1 commit into
mainfrom
e2e-alldevices-tolerate-multicast-tunnel
Open

e2e: tolerate multiple tunnel statuses in all-devices unicast QA test#3976
thijsvanemmerik wants to merge 1 commit into
mainfrom
e2e-alldevices-tolerate-multicast-tunnel

Conversation

@thijsvanemmerik

Copy link
Copy Markdown
Contributor

Summary

  • TestQA_AllDevices_UnicastConnectivity called the deprecated GetUserStatus, which returns an error when a host reports more than one tunnel status. A host that holds both an IBRL and a Multicast tunnel therefore errored and was dropped from the batch, and a batch with fewer than two connected clients times out.
  • Switch the two remaining call sites to GetUserStatuses + FindIBRLStatus, which select the IBRL status (and return the sole status on single-tunnel hosts). A host with a lingering Multicast tunnel is now kept via its IBRL status; a host with no IBRL status is excluded from routing.
  • Log a warning when a host reports more than one tunnel status, so the multi-tunnel condition stays visible without failing the sweep.

Testing Verification

  • Added TestFindIBRLStatus covering: single status returned as-is, IBRL selected when an IBRL and a Multicast status are both present (including IBRLWithAllocatedIP), and nil when no IBRL status exists.
  • go test ./e2e/internal/qa/ -run TestFindIBRLStatus passes; go vet -tags qa ./e2e/... clean.

@thijsvanemmerik thijsvanemmerik force-pushed the e2e-alldevices-tolerate-multicast-tunnel branch from bce0e73 to b2b45d5 Compare July 5, 2026 08:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant