Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Bitbucket Runner, kubernetes 403 errors.

 Trying to get a pipeline runner working in a Kubernetes cluster.

Followed this guide:

When I run the deployment I get the following error in the logs:

[2022-06-20 18:37:30,261] An error occurred whilst updating runner state to "ONLINE".
com.atlassian.pipelines.stargate.client.core.exceptions.StargateForbiddenException: Response Summary: HttpResponseSummary{httpStatusCode=403, httpStatusMessage=Forbidden, bodyAsString={"error":{"message":"Forbidden","detail":"Could not find runner associated with oauth client.","data":{"key":"","arguments":{}}}}}

There is some issue with the actual key? When I check the environment variables the correct key is there.

Any ideas?

1 answer

1 accepted

1 vote
Answer accepted

Found the solution, needed to include the REPOSITORY_UUID environment var!

Hey @justinquaintance  - this has just randomly started happening on our pipelines....where did you set this environment var?

For those who stumble on this - my solution was to upgrade the runners.

Please give me more detail about upgrading the runners. Thanks

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events