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:

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 again. w

Hi Wang, I wrote a blog post you can read about here: http://www.evoila.de/cloud-foundry/adding-diego-release-to-cloud-foundry-release-v212/?lang=en

Hi, yes we are running an installation on Liberty here, without any issues.

If you deploy again (not bosh-init delete), all the data should remain on the detached disk, which is reattached after the deployment if I remember correctly. wrote:

As stated before changed security groups to default_security_groups=[default], then it should work. wrote:

In the CLI command itself

Here you go: #!/bin/bash bosh create-env bosh.yml \ -o openstack/cpi.yml \ --state=/workspace/deployments/bosh-1/state.json \ --vars-store=/workspace/deployments/bosh-1/creds.yml \ -v director_name=bo

No it is just a complete example. Remove the section if you don't need it.

Arpit, you did not specify a domain. Is your OS installation having v2 or v3 API endpoints? wrote:

Arpit, for debugging purpose: please try to download a stemcells and upload it by hand into OS. See if it is working, if not you might have the wrong stemcell. (there is a difference between the forma

Perhaps you have different AvailabilityZones for Nova and Cinder. Please go to the configuration file for OS V2 and add the following entry: ignore_server_availability_zone: true wrote:

Ok hmpf that's interesting. To unterstand it again Arpit, are you able to spawn an instance from Horizon or the CLI with the uploaded Stemcell? wrote:

Hi Arpit, did you check: architecture='x86_64', auto_disk_config='true', hypervisor_type='kvm', os_distro='centos', os_type='linux', version='3421.11' Maybe no Hypervisor of type KVM? wrote:

Then take a look here: https://github.com/cloudfoundry-incubator/bosh-openstack-cpi-release/issues/39 wrote:

Hi Arpit, that means it works? wrote:

Hi Arpit, I would switch to a different hardware and in the meanwhile open a ticket to request configuration of this element as an option on the bosh_openstack_cpi. Best, Johannes wrote:

Hi Arpit, thanks for your kind words. This should be the right place, where you can open a ticket: https://github.com/cloudfoundry-incubator/bosh-openstack-cpi-release/issues wrote:

Hi Arpit, can you see the volume being created in OS? wrote:

Hi Arpit, two important things: - I would not proceed with an installation, if you already run into disk capacity issues now. A minimal useful installation consists of at least 10 - 12 VMs an will con