Can't enable Pipelines: "Account {54c6f884-c96c-4f13-a63f-aae6233c2e4d} does not exist"

Question

Workspace: SputnikFive (UUID {54c6f884-c96c-4f13-a63f-aae6233c2e4d}, created 2018)

Repository: SputnikFive/manmakegame

I can't enable Pipelines on this repository. In Repository settings > Pipelines > Settings, the Enable Pipelines toggle switches on, then reverts after a refresh. Same result in Safari and Chrome. On the repository's Pipelines page, "Run initial pipeline" says Pipelines is disabled for this repository.

Two-step verification is on for my Bitbucket account, I'm the workspace owner, and bitbucket-pipelines.yml is committed on main.

Calling the API directly with a scoped API token (admin:repository:bitbucket):

PUT https://api.bitbucket.org/2.0/repositories/SputnikFive/manmakegame/pipelines_config

{"enabled": true}

returns HTTP 404:

{"error": {"message": "Not found", "detail": "Account {54c6f884-c96c-4f13-a63f-aae6233c2e4d} does not exist.", "data": {"key": "account-service.account.not-found"}}}

That UUID is my workspace. The browser console on the settings page also shows a 404 from:

https://api.bitbucket.org/internal/site/addons/account/{6802dad1-6e19-44a8-af9f-3f57c90b39af}/install/

It looks like the Pipelines record for this workspace is missing. Could you recreate it, or enable Pipelines for the workspace?

Mihai_LeanZero · Answer

Same error key in two other threads in the last two weeks:
https://community.atlassian.com/forums/discussion/3306734
https://community.atlassian.com/forums/discussion/3288488

Three in two weeks. That reads like something on bitbucket's side, probably nothing in the workspace itself.

Same dead ends there too. A bitbucket-pipelines.yml was committed in both, two-step verification was on in the second, and another user in the 3288488 thread got the identical 404 from PUT pipelines_config.

There's an open bug with this exact PUT and error body: https://jira.atlassian.com/browse/BCLOUD-21974
It's filed for repos transferred between workspaces, so it may not be your case, but the workaround in it is quick to try: add a second user as admin on the repo and have them enable Pipelines. Haven't tested it on a repo with no transfer behind it.

If that does nothing, a free plan only gets Community support, so it comes down to staff picking one of these threads up.

SputnikFive · Answer

Thanks Matthew. I don't think a service account is involved here. The UUID in the error, {54c6f884-c96c-4f13-a63f-aae6233c2e4d}, is the SputnikFive workspace itself (it's what GET https://api.bitbucket.org/2.0/workspaces/SputnikFive returns), not a user or service account. It's a free personal workspace from 2018, not part of an Atlassian organization, and there are no service accounts set up.

So it looks like the Pipelines service has no record of the workspace. If anyone from the Bitbucket team sees this, could you check whether the Pipelines account record for this workspace is missing?

Matthew Sinclair · Answer

Can't really speak to Bitbucket or pipelines.

But the Error Message is saying the "Service Account" it was expecting is not present.

You may want to see if the Account is still present in your Org (Org Admin Access required)?

Check configuration to see if Bitbucket is employing an account/actor for an action or other.

Info on Service Accounts:

https://support.atlassian.com/user-management/docs/understand-service-accounts/

If anything the Audit Log in the Org Admin controls may reveal something.

If this has nothing to  do with that - feel free to ignore.