Runners Autoscaler Setup throwing error - You may not have access to this repository or it no longer exists in this workspace
Platform Notice: Cloud Only - This article only applies to Atlassian products on the cloud platform.
Summary
When performing the initial configuration of Runners Autoscaler, it is possible that you will encounter the following error message:
1
You may not have access to this repository or it no longer exists in this workspaceEnvironment
Bitbucket Pipelines Self-hosted Runners using Runner Autoscaler tool.
Cause
There are several root causes for this issue:
The workspace or repository, as well as the runner you are attempting to configure, may no longer exist within Bitbucket.
The OAuth credentials that have been configured for use in the Runner might lack access to one or more resources necessary for the Runner's execution.
There may be an incorrect configuration present in the Kubernetes object specification.
It's a requirement to have the following variables in YAML:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
env:
- name: ACCOUNT_UUID
value: # Add your account uuid here
- name: REPOSITORY_UUID
value: # Add your repository uuid here
- name: RUNNER_UUID
value: # Add your runner uuid here
- name: OAUTH_CLIENT_ID
valueFrom:
secretKeyRef:
name: runner-oauth-credentials
key: oauthClientId
- name: OAUTH_CLIENT_SECRET
valueFrom:
secretKeyRef:
name: runner-oauth-credentials
key: oauthClientSecretIf any of the UUIDs are incorrect, or if the OAuth credentials are not valid, this error message will be displayed.
Solution
Verify the existence of the workspace, repository, or Runner you are attempting to configure in Bitbucket Cloud by utilizing Bitbucket's user interface to navigate to these elements.
Check whether the OAuth credentials possess the necessary access to the resources (Workspace/Runner/Repository) outlined in your Kubernetes object specification.
As the workspace administrator, you can verify this by following the steps outlined below:
Begin by navigating to the workspace settings.
Proceed to select "OAuth credentials."
Locate the OAuth token currently in use for the Autoscaler configuration.
Click on the "..." icon and then select Edit.
Verify whether the OAuth consumer possesses the following permissions:
repository:read, account:read, runner:write
Verify the UUIDs and credentials present in your Kubernetes object specification to ensure they correspond accurately with the data stored in Bitbucket.
Was this helpful?