Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Bitbucket Runner, kubernetes 403 errors.

justinquaintance
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
June 20, 2022

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

Followed this guide: https://janosmiko.com/blog/2021-09-08-bitbucket-pipelines-runners-in-k8s/

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":"rest-service.rest-service.forbidden","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
justinquaintance
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
June 20, 2022

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

Jack Warnes
Contributor
August 1, 2022

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

Jack Warnes
Contributor
August 1, 2022

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

Pham Minh Man
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
December 11, 2022

Please give me more detail about upgrading the runners. Thanks

matwerber1
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
February 24, 2025

@Pham Minh Man I was running into this issue as well. 

 

I installed the BitBucket Autoscaler for Kubernetes using the latest Helm chart as of today from https://github.com/lablabs/bitbucket-runner-autoscaler-helm-chart/tree/main.

 

This creates a configmap named bitbucket-runner-autoscaler/bitbucket-runner-autoscaler-template which contains a line in the job.yaml.template property that specifies a runner image of 

image: docker-public.packages.atlassian.com/sox/atlassian/bitbucket-pipelines-runner:1.
The line above is forcing job runners to use the tag (version) of 1 of the docker image bitbucket-pipelines-runner.


I found that the latest version is actually v3 and that v1 should no longer be used: 
https://www.atlassian.com/blog/bitbucket/bitbucket-pipelines-runner-upgrade-required
To change the runners to use the latest image, I removed the ":1" tag from the image, i.e. I changed the line in the configmap to image: docker-public.packages.atlassian.com/sox/atlassian/bitbucket-pipelines-runner
This causes the runner to pull the latest version. After that, I stopped receiving the error.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events