No IP address asgined to micro bosh instance...

[Prashant .B]

Hi,

After deployment of micro bosh instance, ip address is not assigned to instance.. got below error message.

Waiting for the agent               |oooooo                  | 3/11 00:11:02  ETA: --:--:--at depth 0 - 20: unable to get local issuer certificate

Waiting for the agent               |oooooo                  | 3/11 00:12:02  ETA: --:--:--at depth 0 - 20: unable to get local issuer certificate

Waiting for the agent               |oooooo                  | 3/11 00:13:02  ETA: --:--:--at depth 0 - 20: unable to get local issuer certificate

Waiting for the agent               |oooooo                  | 3/11 00:14:02  ETA: --:--:--at depth 0 - 20: unable to get local issuer certificate

Waiting for the agent               |oooooo                  | 3/11 00:15:02  ETA: --:--:--at depth 0 - 20: unable to get local issuer certificate

Waiting for the agent               |oooooo                  | 3/11 00:16:02  ETA: --:--:--at depth 0 - 20: unable to get local issuer certificate

Waiting for the agent               |oooooo                  | 3/11 00:16:34  ETA: --:--:--Unable to connect to Bosh agent. Check logs for more details.at depth 0 - 20: unable to get local issuer certificate

[David Williams]

Hi Prashant...which CPI (AWS, Openstack, vSphere, vCloud) and which MicroBosh stemcell are you using?

[Prashant .B]

Hi David,

i am using vSphere CPI and micro stemcell version :  micro-bosh-stemcell-vsphere-0.6.4.tgz.

[David Williams]

That's what I was thinking. We ran into the same issues...and not just for MicroBOSH, but for BOSH and CF, too.

For vSphere 5.1.x CPI, we found that the following stemcells work best:

- Stemcell 785 for MicroBOSH
- Stemcell 808 for BOSH
- Stemcell 1.5.0-pre2 for CF releases 133/134

Note that when we tried 786 for MicroBOSH, the same issue with no IP occurred. Haven't tested a Stemcell higher than those listed above for BOSH or CF release yet.

Hope that helps...

[David Williams]

Quick update...I noticed that the public stemcell list now includes 1.5.0-pre2 for both MicroBOSH and BOSH.  They didn't previously.  I'm not sure whether those are the same as the ones I listed before, newer, or older; and we haven't tested them yet.  By the versioning, though, it does seem to imply that you could use the same version for all 3 deployments.  Again, we haven't tested this yet.

FYI...those stemcells only show up if you run

bosh public stemcells --all

[Prashant]

Hi David,

Could you please post the complete URL for stemcells mentioned above by you, because i cannot find them under public stemcells.

--
REGARDS ,
PRASHANT B

[Prashant]

Hi David,

could you please share the complete URL to download the stemcells...

[David Williams]

Sure thing.  There isn't really a single URL to find all of the stemcells.  Instead, refer to this listing:

http://bosh-jenkins-artifacts.s3.amazonaws.com/

Each stemcell listed has an attrbute called "key".  Append "key" to the URL provided above to download the .tgz.  For example, if I wanted to download build 870 for micro-bosh on vSphere (micro-bosh-stemcell-vsphere-870.tgz) and it had a Key of micro-bosh-stemcell/vsphere/micro-bosh-stemcell-vsphere-870.tgz, then the URL to download the .tgz would be:

http://bosh-jenkins-artifacts.s3.amazonaws.com/micro-bosh-stemcell/vsphere/micro-bosh-stemcell-vsphere-870.tgz

[Prashant .B]

Hi David,

thanks for the update. it works and i can see the IP's are gettting assigned for Micro Bosh and Bosh instances. but when i try to target to my bosh director i get the below error message...

cfadmin@cfserver:~/deployments$ bosh target 10.209.32.134
Perform request get, https://10.209.32.134:25555/info, {"Content-Type"=>"application/json"}, nil
REST API call exception: SSL_connect SYSCALL returned=5 errno=0 state=unknown state

Please let me know how to fix this SSL problem. logs are attached.