Error deploying CF on virtualbox using Bosh

Question

I am using mac OS and trying to deploy CF on virtualbox using BOSH.

BOSH Director installed has the following details

$ bosh -e vbox env
Using environment '192.168.50.6' as user 'admin'

Name      bosh-lite  
UUID      bbdcc68d-5390-4d08-bd80-900bf3aa3551  
Version   268.2.0 (00000000)  
CPI       warden_cpi  
Features  compiled_package_cache: disabled  
          config_server: enabled  
          local_dns: enabled  
          power_dns: disabled  
          snapshots: disabled  
User      admin  

Bosh CLI version is

version 5.4.0-891ff634-2018-11-14T00:21:14Z

To deploy CF, I run the following script

bosh -e 192.168.50.6 -d cf deploy \
  cf-deployment.yml \
  -o operations/bosh-lite.yml \
  -v system_domain=bosh-lite.com

I get the following error:

Task 33 | 15:26:34 | Updating instance diego-api: diego-api/95e076b7-0fc4-43e0-9db6-afbd8b79d76d (0) (canary) (00:20:19)
                   L Error: 'diego-api/95e076b7-0fc4-43e0-9db6-afbd8b79d76d (0)' is not running after update. Review logs for failed jobs: bbs, silk-controller, locket
Task 33 | 15:46:53 | Error: 'diego-api/95e076b7-0fc4-43e0-9db6-afbd8b79d76d (0)' is not running after update. Review logs for failed jobs: bbs, silk-controller, locket

Task 33 Started  Fri Nov 16 15:24:57 UTC 2018
Task 33 Finished Fri Nov 16 15:46:53 UTC 2018
Task 33 Duration 00:21:56
Task 33 error

Updating deployment:
  Expected task '33' to succeed but state is 'error'

Exit code 1

cf-deployment file and ops file (from iaas/bosh-lite/cloud-config.yml) folder) that I use are from

https://github.com/cloudfoundry/cf-deployment

I also uploaded ubuntu-xenial stemcell that the cf-deployment file uses

There is a similar issue reported here

https://github.com/cloudfoundry/cloud_controller_ng/issues/1047

but I couldn't really gather the solution.

Is there a way to resolve this issue and move on ?

Answer 1

I had the same issue and found this github issue

To fix it I executed:

bosh update-runtime-config bosh-deployment/runtime-configs/dns.yml --name dns

I hope this fixes your problem as well ;)

Answer 2

I found the above answer works if you have UAA and Credhub deployed. If you are using vars-store, I found the following issue to be relevant:

https://github.com/cloudfoundry/cf-deployment/issues/617

The command from above changes slightly:

bosh -e vbox update-runtime-config <(bosh int bosh-deployment/runtime-configs/dns.yml --vars-store deployment-vars.yml) --name dns

I think the gist is that you are feeding replacement variables found in dns.yml with the value found in deployment-vars.yml and the result is fed into update-runtime-config.