tailscale / tailscale/github-action

Tailscale up command results in infinite loop of connection status

Open
#128 13 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

needs-triage
Dominant language
TypeScript
Stars
938
Forks
137
PR merge metrics
No merged PRs in 30d

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

image
image

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

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.

Assessment

Tech stack
github-actions, typescript
Domain
ci-cd
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
32/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.