Getting HTTP 429 Error when using self-hosted-runners

[renatomotacaju]

What happened?

Am I missing something? the code is bellow, on example

Example

jobs:
  staging:
    name: Update staging
    runs-on: [Linux, self-hosted, deploy-staging]
    steps:
      - uses: actions/checkout@v4
      - name: Setup Python
        uses: actions/setup-python@v4
        with:
          python-version: 3.11
          cache: pip

      - name: Configure AWS Credentials
        uses: aws-actions/configure-aws-credentials@v4
        with:
          aws-access-key-id: ${{ secrets.AWS_ACCESS_KEY_ID }}
          aws-region: sa-east-1
          aws-secret-access-key: ${{ secrets.AWS_SECRET_ACCESS_KEY }}
      
      - name: Installing PyPi dependencies for Pulumi
        run: |
          python3 -m venv venv
          source venv/bin/activate
          pip install --upgrade pip
          pip install -r requirements.txt
          
      - uses: pulumi/actions@v5
        name: Deploy Staging
        with:
          command: up
          stack-name: staging 
          work-dir: src
          suppress-outputs: true
          suppress-progress: true
        env:
          PULUMI_ACCESS_TOKEN: ${{ secrets.PULUMI_ACCESS_TOKEN }}

getting the following error, only on self-hosted:

HTTPError: Response code 429 (Too Many Requests)
    at Request.<anonymous> (/runner/_work/_actions/pulumi/actions/v5/webpack:/pulumi-github-action/node_modules/got/dist/source/as-promise/index.js:118:1)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)

Output of pulumi about

couldnt figure out how to do on github actions.

locally it works fine

local:

❯ pulumi about
CLI          
Version      3.202.0
Go Version   go1.25.2
Go Compiler  gc

Plugins
KIND      NAME    VERSION
resource  aws     7.9.1
resource  kafka   3.12.1
language  python  3.202.0

Host     
OS       darwin
Version  26.0.1
Arch     arm64

This project is written in python: executable='/Users/renato.mota/Repositories/pulumi-poc/src/venv/bin/python' version='3.13.7'

Current Stack: renatomotacaju-org/pulumi-kafka/staging

TYPE                     URN
pulumi:pulumi:Stack      urn:pulumi:staging::pulumi-kafka::pulumi:pulumi:Stack::pulumi-kafka-staging
pulumi:providers:kafka   urn:pulumi:staging::pulumi-kafka::pulumi:providers:kafka::kafka-staging
pulumi:providers:kafka   urn:pulumi:staging::pulumi-kafka::pulumi:providers:kafka::kafka-staging-iam
kafka:index/topic:Topic  urn:pulumi:staging::pulumi-kafka::kafka:index/topic:Topic::staging-pulumi-poc-staging
kafka:index/topic:Topic  urn:pulumi:staging::pulumi-kafka::kafka:index/topic:Topic::staging-iam-pulumi-poc-staging-iam
kafka:index/topic:Topic  urn:pulumi:staging::pulumi-kafka::kafka:index/topic:Topic::staging-iam-pulumi-poc-staging-iam-2


Found no pending operations associated with staging

Backend        
Name           pulumi.com

Token type     personal

Dependencies:
NAME          VERSION
pulumi_aws    7.9.1
pulumi_kafka  3.12.1
setuptools    80.9.0
wheel         0.45.1

Pulumi locates its logs in /var/folders/3k/w53p4pt55r5bcdpd0qnb2x580000gp/T/ by default

Additional context

No response

Contributing

Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).

[renatomotacaju]

It worked randomly one time and never again :(

[tgummerer]

Hi @renatomotacaju, sorry for the trouble here.

Looking at the error message this error seems to come from the got library. We're only using that for getting the version here. So it looks like you're getting a 429 from GitHub for some reason. 429 indicates too many requests, so maybe something in your infrastructure is getting rate limited since you mention self-hosted.

As a workaround/to try that theory out, you can maybe use

with:
  pulumi-version: dev

in your pulumi/actions block. This will install the dev version of Pulumi, but will get it from S3 directly instead of downloading from GitHub. If that works the issue must be somewhere within your self hosting setup (sometimes setting a GITHUB_TOKEN could help increase the rate limit), but it's hard to debug without having access to that.