Hello! I have a question about resurrection algorithm BOSH uses in multi zone deployment. Suppose we have three availability zones: z1, z2 and z3. We have data/0 vm in z1 with resurrection

*bosh task 8 --debug* helped to find cause of the problem. I referenced Open Stack authorisation API using host name and it resolved to the wrong IP address. When endpoint was referenced using IP

It would be easier to find out what’s the problem if you’ll provide stack traces of this error. It would be great if you to share both director and CPI stack traces. Talking about environment, I

It seems that nabble eats your text from console. Could you please provide us with stack trace of this error? I’m sure you can find it in a CPI log.

I try to upload stemcell to bosh director but fail with error: I tried 3022 and 2719.3 openstack-kvm-ubuntu-trusty-go_agent stemcells, both failed. How can I fix it? My environment: P.S.

The first format is normally easier to read. To be valid YAML, ensure there are only spaces for indentation, and not tab characters. The second format will also work, but you need to make double line

Hi Mathias, I faced the same issue on vSphere with NFS. At the following to the property section of your properties in cf-stub.yml: debian_nfs_server: no_root_squash: true And run bosh deploy

Hello Matthias, The issue i hit was a bug. It cause cos i was using NFS. I removed NFS server and used S3 bucket (Credit goes to Pablo Alonso Rodriguez). then i was able to deploy successfully. See

couple more: /var/vcap/sys/log/cloud_controller_worker_ctl.err.log [2015-07-24 12:22:57+0000] ------------ STARTING cloud_controller_worker_ctl at Fri Jul 24 12:22:57 UTC 2015

I noticed this in

Hi Matthias, did you get into api_z1 0 via ssh and look at the specific error? The problem here is, that the failure might arise from different sources. wrote: -- Mit freundlichen

Dulanjalie, did you ever get this resolved? I am running into the same issue, with a blank-slate 212 install: Failed updating job api_z1 > api_z1/0 (canary): `api_z1/0' is not running after

Hi Gwenn, Thanks for clearing up my misunderstanding. Thanks Daya From: <cf-bosh-bounces(a)lists.cloudfoundry.org<mailto:cf-bosh-bounces(a)lists.cloudfoundry.org>> on behalf of Gwenn Etourneau

Hi Expert, What is the right format to add cert/private key into ssl_pem? My environment: BOSH 1.3016.0 CF-release：213 Stemcell: 3012 vSphere 5.5 u2 Ubuntu 14.04 bosh cli, VI to edit file. HA

That's two different things ... One use diego to run container into CF and the second one run container into a VM without any scheduling and so on...Mostly the same as "docker run" ... So

I read this thread https://lists.cloudfoundry.org/pipermail/cf-dev/2015-July/000720.html and Eric mentions in his reply that the current support level is mentioned under

Seems "bosh aws create" will read bosh file from s3, in the past, the command is executed successfully except for "creating database". The command "bosh aws create" tries to continue executing, after

Error seems to be "The vpc ID 'vpc-e4484c81' does not exist (AWS::EC2::Errors::InvalidVpcID::NotFound)" no ?

I guess you need to setup the users & their shared keys within a job template