Tailscale up command results in infinite loop of connection status
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 32/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- github-actions, typescript
- Domain
- ci-cd
Research direction
Start with the workflow shown in the issue, comparing the two tailscale/github-action@v2 invocations and their repeated connection-status logs. Reproduce the behavior with version 1.66.3 and the --exit-node=pfsense argument, then trace the action entry point to determine whether the second invocation is handled correctly. Done means the loop is fixed or the supported usage and failure cause are clearly documented.
Written by the indexing model from the issue text.
Description
I'm running the following in a github action, in previous versions it typically connects then when I call the up command again with an --exit-node value it will sometimes result in this constant repeating log of all 0's for many minutes until it times out. Am I using the action incorrectly given recent updates?
- name: Tailscale
uses: tailscale/github-action@v2
with:
oauth-client-id: ${{ secrets.CLIENTID }}
oauth-secret: ${{ secrets.SECRET }}
tags: tag:ci
version: 1.66.3
#args: "--exit-node=pfsense" #using this we get an error: must be IP or unique node name
- name: Tailscale - ReRun Up Command To Set ExitNode to pfsense
uses: tailscale/github-action@v2
with:
oauth-client-id: ${{ secrets.CLIENTID}}
oauth-secret: ${{ secrets.SECRET }}
tags: tag:ci
args: "--exit-node=pfsense"
version: 1.66.3
- 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
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 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 78/100
fullcalendar/fullcalendar#8106 ·