-
Notifications
You must be signed in to change notification settings - Fork 33
CPI 'create_stemcell' method responded with error: read timeout reached #106
Comments
Since you're using a proxy, you'll need to add an
And also add |
Hi, Thanks for the response. Unfortunately it still doesn't go through. Could you confirm that this is the step where it is trying to upload the stemcell to OpenStack? If you can point me to towards the API that it is using, I can manually check if the API is working? Thanks |
Hi @srinat999, Yes, it's the step where the BOSH OpenStack CPI uploads the stemcell. Here you can find which APIs are used for this in case of Image Service API v2. Which version do you have?Documentation about OpenStack Image Service API v2 is here Beyhan |
Hi @beyhan I investigated the issue with OpenStack and it was indeed a problem with the image upload API. I fixed it and so I was able to progress further. However, in the instance creation step the process fails. This is the error that I get:
I also tried the api for creating an instance:
This works and the instance is created. What do you think the problem is? Thanks |
Hi @srinat999, Error happens after VM creation. Bosh-init fails to update the BOSH registry with the settings of the VM which has been created. Bosh-init starts a BOSH registry on your machine where bosh-init is executed. The registry is required for the deployment and it's available on port |
So I was trying to bootstrap a BOSH environment on OpenStack using the instructions given here and I got this error at the bosh-init deploy step
I'm assuming this is the step where it is trying to upload the stemcell as an image to the OpenStack and for some reason it is failing. I'm not sure whether its an error at my OpenStack side as creation of a normal Ubuntu server image from here also throws an error in OpenStack.
For reference here is my bosh.yml
I'm also under a proxy and I have added the relevant IPs to my no_proxy variable.
The text was updated successfully, but these errors were encountered: