Bitbucket Pipelines Runners on Kubernetes fail on the initial configuration with error Property: 'bitbucket.pipelines.runner.account.uuid' is not configured correctly.
Platform Notice: Cloud Only - This article only applies to Atlassian products on the cloud platform.
Summary
When setting up a Docker-based Runner to Kubernetes, it is essential to follow the steps outlined on this page. During this process, you may encounter an error message that includes a detailed Java stack trace. In certain instances, the following error message might be present within the stack trace:
1
Property: 'bitbucket.pipelines.runner.account.uuid' is not configured correctly.
Environment
Bitbucket Pipelines Runners using Kubernetes autoscaler.
Diagnosis
When configuring Kubernetes for the deployment of a Docker-based runner, it is possible to encounter an error message within the stack trace after finalizing the Kubernetes configuration as outlined on this page.
1
Property: 'bitbucket.pipelines.runner.account.uuid' is not configured correctly.
Cause
This issue arises from an improper configuration of your Kubernetes object spec. Specifically, one of the UUIDs that must be included in the Kubernetes object spec file is incorrect, which leads to the failure of the initial configuration process.
Solution
Reviewing your Kubernetes object specification is essential for ensuring proper configuration and functionality. Please verify whether the specified section is present within the object. Additionally, confirm that the UUIDs listed in the file correspond accurately to the appropriate Account UUID, Repository UUID, and Runner UUID values.
1
2
3
4
5
6
7
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
Was this helpful?