Provisioning Service returned status code: 503

Feedback & Bug Reports
1

This morning setup_remote_docker step started to fail with error message:

 Allocating a remote Docker Engine
Got error while creating host: rpc error: code = Unknown desc = An internal error occured when provisioning resources for this job.  Provisioning Service returned status code: 503
We had an unexpected error preparing a VM for this build, potentially due to our infrastructure or cloud provider.  Please retry the build in a few minutes

Waited 15 min and still on all repeats the same outcome.

3 Likes
2

Had the same output, it changed now but still not able to build

Allocating a remote Docker Engine
Got error while creating host: rpc error: code = Unknown desc = Put https://vm-service.infra.circleci.com/tasks/5ae02e4c210898001429b6a1-0-build%2F57934B2C: dial tcp 172.16.37.163:443: getsockopt: connection refused
We had an unexpected error preparing a VM for this build, potentially due to our infrastructure or cloud provider. Please retry the build in a few minutes

3

It’s presently noted on the status page.

4

Similar thing happened to me too.

Blockquote
Build-agent version 0.0.4869-fac853b (2018-04-17T20:59:55+0000)
Creating a dedicated VM with default image
We had an unexpected error preparing a VM for this build, potentially due to our infrastructure or cloud provider. Please retry the build in a few minutes
Unexpected environment preparation error: Put https://vm-service.infra.circleci.com/tasks/5ae02e04e3a5de001359103b-0-build%2F7BC24CE9: dial tcp 172.16.21.199:443: getsockopt: connection refused

5

This is quite annoying, there’s not much info from circle ci guys, I’ve been stuck with this issue for almost 3 hour now.

2 Likes
6

managed to get one build fixed but now stuck at:

Allocating a remote Docker Engine
Waiting for a Docker Engine assignment: …

Got error while creating host: instance not ready yet: unassigned
We had an unexpected error preparing a VM for this build, potentially due to our infrastructure or cloud provider. Please retry the build in a few minutes.

7

This has been going on for hours and their status page still just shows degradation of service. Our entire pipeline is stuck as none of our builds pass. Has anyone got any communication from them on how long will it take them to fix this?

8

that sucks, I’m also waiting for someone from circle ci to at least explain what’s going on. :smiley:

9

I do know that circle ci team is working on it because I started getting a different error, (they probably sent a fix, which didn’t work, and though, ahh, wait, have to do that), I hope it to be fixed within 2 hours from now (if they decide not to wait for their build to pass and directly send a hot fix)

(maybe their build is also failing :smiley: that’d be funny)

10

We’re having the same issue,

Build-agent version 0.0.4869-fac853b (2018-04-17T20:59:55+0000)
Creating a dedicated VM with default image
We had an unexpected error preparing a VM for this build, potentially due to our infrastructure or cloud provider. Please retry the build in a few minutes
Unexpected environment preparation error: Put https://vm-service.infra.circleci.com/tasks/5ae04fac533a420007b551c4-0-build%2F1B6BD981: dial tcp 172.16.6.26:443: getsockopt: connection refused

11

https://status.circleci.com/ shows that issue has been fixed and for me it is again working

12

looks like it’s been resolved

13

While everyone waits, folks can browse Twitter for petulant, passive-aggressive and ill-mannered examples of how not to complain. :roll_eyes:

2 Likes
14

Thanks for your patience everyone. The issue is now resolved.

15

Who can help us?

16

Same here, is beginning to hold back devs.

17

Help you with what? :smiley_cat:

18

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.