AWS Codebuild Projects stuck in SUBMITTED Status. Outage?

Question

All of our codebuild jobs have been stuck in Submitted phase (the Queued phase is shown with no status). They worked earlier in the day and we haven't changed anything about the configuration

I've checked and there's no outage reported on the AWS health page.

Is there an unreported codebuild outage?

Accepted Answer

Had to get on the phone with AWS support, turned out to be an issue with AWS. After working with them for awhile we were able to resolve it but only after escalating it. Here's details from that support issue:

> In order to test if this was truly a concurrency issue, I had you manually stop all current builds. After all builds were stopped, your current running count should have been "0". Once the count was 0, you attempted to manually start a new build through the console. From here, we witnessed the build get stuck again in the QUEUED state. Because you were unable to provision just one CodeBuild job, we were able to confirm that this was not an expected behavior. At this point in time, I escalated this to the internal team. While working with them, we checked the backend and believed there was an issue with how the running builds were being counted. After resetting certain properties on the backend, you were then able to successfully provision new builds through your GitHub Webhooks.

Hopefully useful to somebody else

Answer

What is the AWS region ? I would reach out to AWS PS Support for the Code-build team. There is no global outage happening. Had there been an outage which is acknowledged, it would have been reported in the PHD or through an email on the registered email account.

AWS Codebuild Projects stuck in SUBMITTED Status. Outage?

Contenus pertinents