Hi ,

We've been using microbosh -> bosh -> CF model in AWS.. I tried to use bosh-init and able to deploy microbosh successfully..When I am trying to upload stemcell (As part of deploying bosh) ,I am getting following error..

Started update stemcell > Uploading stemcell bosh-aws-xen-hvm-ubuntu-trusty-go_agent/3012 to the cloud. Failed: Unknown CPI error 'Unknown' with message 'execution expired' (00:01:12)

Error 100: Unknown CPI error 'Unknown' with message 'execution expired'
..
Seems like dns issue..I used same manifest as mentioned above..My AWS security groups looks good
When I login to microbosh, nslookup doesnt work..
My resolv.conf says, nameserver 10.0.1.2 ( I am using 10.0.1.0/24 subnet),which seems correct..

Did anyone encounter similar issue? Appreciate any inputs..

I am getting confused here...Is there any reason to deploy bosh after deploying micro-bosh using bosh-init? Doesn't it serve same purpose as bosh ? Really appreciate if someone can educate me..

I was able to resolve issue by changing dns host to 10.0.0.2..Please ignore my first question.

Is there any reason to deploy bosh after deploying micro-bosh using

bosh-init?

Not in my opinion regardless if you are using bosh-init or micro CLI plugin.

Regarding error from bosh-init, you can try turning on verbose logging:
export BOSH_INIT_LOG_LEVEL=debug

On Tue, Oct 13, 2015 at 1:59 PM, Satya Thokachichu <tsnraju(a)yahoo.com>
wrote:

I was able to resolve issue by changing dns host to 10.0.0.2..Please
ignore my first question.