Tailscale routes missing in ephemeral runners
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 38/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- github-actions
- Domain
- ci-cd, networking
Research direction
Start by reproducing the workflow with the shown Tailscale setup and compare ip route show table all | grep tailscale on failing and working runners. Check the action's setup flow around route initialization, then verify that the expected route is present and curl succeeds without running tailscale down && tailscale up.
Written by the indexing model from the issue text.
Description
Hello team!
We are using the action to run a simple curl request in our tailnet, and it has been failing randomly. After some digging, we noticed the following:
- Tailscale ping does work (for the DN and IP requested). We tried manually, and through the the action
ping: <dn>,<ip> - Once a runner is failing, it does not recover by itself (even after 10 minutes). Curl still fails after that.
- We noticed some routes are missing
ip route show table all |grep tailscaleonly shows the following:
fe80::/64 dev tailscale0 proto kernel metric 256 pref medium
local fe80::ba:54d9:b084:82e9 dev tailscale0 table local proto kernel metric 0 pref medium
multicast ff00::/8 dev tailscale0 table local proto kernel metric 256 pref medium
While on a working runner, we do have the desired route showing.
Hotfix: a simple tailscale down && tailscale up in the action does solve the issue.
Current action is as follow:
- name: Setup Tailscale
uses: tailscale/github-action@53acf823325fe9ca47f4cdaa951f90b4b0de5bb9 # v4.1.1
with:
version: TAILSCALE_VERSION
oauth-client-id: <some-client-id>
oauth-secret: <some-client-secret>
tags: tag:<some-tag>
ping: <some-internal-ips>,<some-internal-dn>
Thank you!
Jules
- Dominant language
- TypeScript
- Stars
- 938
- Forks
- 137
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from tailscale/github-action
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
tailscale/github-action#283 · 1 comment · 1 reaction ·
-
fr
Difficulty 3/5 1-2 days Newbie friendliness 68/100
tailscale/github-action#317 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 48/100
tailscale/github-action#316 · 2 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 52/100
tailscale/github-action#315 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 76/100
tailscale/github-action#313 · 1 reaction ·
All issues in tailscale/github-action
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
copse-dev/agent-pane#2953 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Eynzof/Hermes-CN-Desktop#610 ·
-
bug clawsweeper:linked-pr-open clawsweeper:needs-live-repro clawsweeper:no-new-fix-pr impact:message-loss issue-rating: 🐚 platinum hermit P2 regression
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
calcite-components needs triage refactor
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Esri/calcite-design-system#15203 ·