Skip to content

test(mesh): host_network direct-path check can see the runner's public endpoint #189

Open

Description

@Mearman

The host_network mesh scenario failed once on a hosted runner at assert_direct_paths, after every other check had passed:

FAIL: grtest-node1 reaches grtest-node3 only indirectly: pong from grtest-node3 (100.64.0.3) via <the runner's public address>:58418 in 0s

The path was direct, but it went to the endpoint Tailscale learnt over STUN (the runner's public address, hairpinned back through its NAT) rather than node 3's daemon address on the test network, which the check requires. node1 to node2 in the same run went over 172.31.250.12. A rerun of the job passed.

Failed run: https://github.com/ExaDev/github-runner/actions/runs/41616497532/job/125851142782 (PR #186, which does not change this scenario).

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions