Bitbucket Runners - Self hosted - 403 errors

[Jack Warnes]

We have suddenly started receiving these errors on our self-hosted runners:

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":{}}}}}

The error is very random, happens on different projects. There have been no changes to our pipeline.yml files or permissions in our BB instance.

I've upgraded all of our runners to the latest version but still seeing the issue.

Any ideas?

[Jack Warnes · Accepted solution]

I understand this is now fixed on the Bitbucket side.

[Р000-Владимир]

I've just killed all previsious images and containers, run with 

Runner version:
current: 1.342
latest: 1.342

and it's alive  

[Grigory Kazachenkov]

Great! Did the same. Works! Thank you! Looks like they have just updated worker images

[Jack Warnes]

I did try this earlier without much success...

[Р000-Владимир]

What versions do you have ?

[Jack Warnes]

same, 1.342. It's working now after BB fixed it on their side.

[Grigory Kazachenkov]

Hello! Can just approve. We have 2 runners on our kubernetes platform and both of them receive such errors

[Jack Warnes]

When did you start receiving the 403s?

[Grigory Kazachenkov]

I noticed that about an hour ago. But there were no builds before

[Jack Warnes]

Same - 3pm UTC.

[Grigory Kazachenkov]

And our runners are updated to the latest version

[Grigory Kazachenkov]

Now my builds are stuck in Queued state. No error but also they are not assigned to runner. Looks like there is some global problem in bb pipelines.

[Jack Warnes]

I've tried to raise a separate ticket with BB

[Jack Warnes]

Received a response, they're aware of the issue and are looking to fix.

[Craig.Dawson]

We are also seeing this issue.

[Jonathan Gafner]

We are also seeing this issue.