Not able to upload stemcell
Dear Team,
I have deployed bosh director on Openstack ocata(Latest version). But when I am trying to upload stemcell, it gets failed: [root(a)node1 cf-release]# bosh -e bosh-1 upload-stemcell https://bosh.io/d/stemcells/bosh-openstack-kvm-ubuntu-trusty-go_agent Using environment '10.100.10.18' as client 'admin' Task 34 07:01:12 | Update stemcell: Downloading remote stemcell (00:00:20) L Error: Downloading remote stemcell failed. Check task debug log for details. 07:01:32 | Error: Downloading remote stemcell failed. Check task debug log for details. Started Mon Jul 31 07:01:12 UTC 2017 Finished Mon Jul 31 07:01:32 UTC 2017 Duration 00:00:20 Task 34 error Uploading remote stemcell 'https://bosh.io/d/stemcells/bosh-openstack-kvm-ubuntu-trusty-go_agent': Expected task '34' to succeed but state is 'error' Exit code 1 Can anyone help me regarding this? |
|||||||||||||||||||||||
|
|||||||||||||||||||||||
Re: bosh resurrection question
강경원 <atplus12345 at gmail.com...>
On Jul 29, 2017 12:42 AM, "Geoff Franks" <geoff(a)starkandwayne.com> wrote:
Are you triggering meltdown mode on the director, because it's detecting |
|||||||||||||||||||||||
|
|||||||||||||||||||||||
BOSH 261.4 can't find job properties
Jonathan Stockley
Hi,
We have a release with two jobs: job1 and job2. Job1 defines a property, “password" in it’s spec file metadata. One of the job template files in job2 refers to the “password" property defined in job1 but it is not defined in the spec file metadata for job2. This has not caused problems with 255.12 but deploying to BOSH 261.4 we get the following: Error 100: Unable to render instance groups for deployment. Errors are: - Unable to render jobs for instance group ’test'. Errors are: - Unable to render templates for job ‘job2'. Errors are: - Error filling in template 'Config.sh.erb' (line 20: undefined method `password' for nil:NilClass) ‘password’ is the property defined in job1. The properties are defined globally in the deployment manifest. It would appear that the 261.4 BOSH release requires all properties shared between jobs to be defined in each job’s spec file. However, in the documentation https://bosh.io/docs/jobs.html is says 'properties [Hash, optional]: Configuration options supported by the job.’ which tells me that the properties are optional. Can someone explain what the correct behavior is supposed to be now? Thanks, Jo |
|||||||||||||||||||||||
|
|||||||||||||||||||||||
Re: bosh resurrection question
Geoff Franks <geoff@...>
Are you triggering meltdown mode on the director, because it's detecting too many VMs going offline at the same time?
toggle quoted message
Show quoted text
You can `grep -i meltdown` in the logs to be certain. Might need to adjust some of the settings mentioned here: https://bosh.io/docs/resurrector.html#enable On Jul 28, 2017, at 3:57 AM, 강경원 <kyungwon.kang(a)samsung.com> wrote: |
|||||||||||||||||||||||
|
|||||||||||||||||||||||
Re: Error with bosh director deployment
Hi Adrian,
I have removed these parameter from file -v openstack_domain=Default -v openstack_project=admin instead of these you need to enter tenant. As these are not available in keystone V2. |
|||||||||||||||||||||||
|
|||||||||||||||||||||||
Re: Error with bosh director deployment
Hi Adrian,
I have removed these parameter from file -v openstack_domain=Default -v openstack_project=admin instead of these you need to enter tenant. As these are not available in keystone V2. |
|||||||||||||||||||||||
|
|||||||||||||||||||||||
bosh resurrection question
강경원 <kyungwon.kang at samsung.com...>
Does Bosh resurrect only 1 vm for each interval (time_threshold)? When we test it's not recreating multiple down instances simultaneously.
Name bosh-test
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
Re: Error with bosh director deployment
Adrian Monter
Hi Arpit,
Could you tell me what change you made in the file? i have the same problem Thanks. |
|||||||||||||||||||||||
|
|||||||||||||||||||||||
Re: Error with bosh director deployment
Adrian Monter
Hi everyone,
I have the same error "Missing key" You could correct it? creating stemcell (bosh-openstack-kvm-ubuntu-trusty-go_agent 3421.9): CPI 'create_stemcell' method responded with error: CmdError{"type":"InvalidCall","message":"Arguments are not correct, details: 'Invalid OpenStack cloud properties: #\u003cMembrane::SchemaValidationError: { openstack =\u003e { tenant =\u003e Missing key } }\u003e'","ok_to_retry":false} Thanks |
|||||||||||||||||||||||
|
|||||||||||||||||||||||
Share samllest manifest stub file for Cloudfoundry on Openstack
Dear Team,
Example stub file is too long. It is compulsory to use all things according this stub file? Any other way to make this task easy. I dont want to use blobstorage. Is it compulsory to include this blokc also? Thanks & Regards: Arpit Sharma |
|||||||||||||||||||||||
|
|||||||||||||||||||||||
Re: Creating vm with stemcell failed.... No valid host was found. There are not enough hosts available..Filter ImagePropertiesFilter returned 0 hosts
Hi Tyler Schultz,
Thanks for your response. Now I got my point. let me do some efforts with that. |
|||||||||||||||||||||||
|
|||||||||||||||||||||||
Re: Creating vm with stemcell failed.... No valid host was found. There are not enough hosts available..Filter ImagePropertiesFilter returned 0 hosts
Tyler Schultz
Arpit,
More recent versions of the stemcell remove the vcap user's root privileges. To gain root access, you can use [cloudfoundry/os-conf-release/jobs/user_add]( https://github.com/cloudfoundry/os-conf-release/tree/master/jobs/user_add). This release job will add a user with root privileges. Alternatively you can use the [cloudfoundry/bosh-deployment]( https://github.com/cloudfoundry/bosh-deployment) repo. This is a routinely updated way to deploy the latest versions of director. This repo makes reference to the aforementioned user-add release: https://github.com/cloudfoundry/bosh-deployment/blob/master/docs/jumpbox-user.md . --Tyler On Tue, Jul 25, 2017 at 7:05 AM, Arpit Sharma <arpitvipulsharma(a)gmail.com> wrote: Hi Tushar & Johannes, |
|||||||||||||||||||||||
|
|||||||||||||||||||||||
Re: Is Bosh is compatible with Openstack Ocata Version?
Hi All,
I have deployed bosh director on openstack ocata version. Right now it is working ok. I will update you once I have done with cloudfoundy installation. |
|||||||||||||||||||||||
|
|||||||||||||||||||||||
Re: Creating vm with stemcell failed.... No valid host was found. There are not enough hosts available..Filter ImagePropertiesFilter returned 0 hosts
Hi Tushar & Johannes,
This time i have done setup on 8 core srever with ocata version of openstack. I know ocata is not compatible with bosh right now. But I think it should work. Bosh director deployment has been done successfully as shown below message. I am also able to login with vcap user. But still I am not able to get root access. Started validating Downloading release 'bosh'... Skipped [Found in local cache] (00:00:00) Validating release 'bosh'... Finished (00:00:01) Downloading release 'bosh-openstack-cpi'... Skipped [Found in local cache] (00:00:00) Validating release 'bosh-openstack-cpi'... Finished (00:00:00) Validating cpi release... Finished (00:00:00) Validating deployment manifest... Finished (00:00:00) Downloading stemcell... Skipped [Found in local cache] (00:00:00) Validating stemcell... Finished (00:00:03) Finished validating (00:00:06) Started installing CPI Compiling package 'ruby_openstack_cpi/6576c0d52231e773f4ad53f5c5a0785c4247696a'... Finished (00:03:08) Compiling package 'bosh_openstack_cpi/918abecbb3015ee383d5cb2af23e8dbfed6392d1'... Finished (00:00:03) Installing packages... Finished (00:00:00) Rendering job templates... Finished (00:00:00) Installing job 'openstack_cpi'... Finished (00:00:00) Finished installing CPI (00:03:12) Starting registry... Finished (00:00:00) Uploading stemcell 'bosh-openstack-kvm-ubuntu-trusty-go_agent/3421.9'... Finished (00:00:08) Started deploying Creating VM for instance 'bosh/0' from stemcell 'b61f7cac-b039-4f8e-b90f-21296d170528'... Finished (00:00:51) Waiting for the agent on VM '3b17e4e7-4ccf-4984-a43e-0713e8f9974c' to be ready... Finished (00:00:52) Creating disk... Finished (00:00:07) Attaching disk 'ee06c19f-55fb-413c-b185-12a125433331' to VM '3b17e4e7-4ccf-4984-a43e-0713e8f9974c'... Finished (00:00:20) Rendering job templates... Finished (00:00:03) Compiling package 'ruby_openstack_cpi/6576c0d52231e773f4ad53f5c5a0785c4247696a'... Finished (00:04:50) Compiling package 'ruby/c1086875b047d112e46756dcb63d8f19e63b3ac4'... Skipped [Package already compiled] (00:00:00) Compiling package 'mysql/b7e73acc0bfe05f1c6cbfd97bf92d39b0d3155d5'... Skipped [Package already compiled] (00:00:00) Compiling package 'libpq/661f5817afe24fa2f18946d2757bff63246b1d0d'... Skipped [Package already compiled] (00:00:00) Compiling package 's3cli/bb1c1976d221fdadf13a6bc873896cd5e2433580'... Skipped [Package already compiled] (00:00:00) Compiling package 'bosh_openstack_cpi/918abecbb3015ee383d5cb2af23e8dbfed6392d1'... Finished (00:00:04) Compiling package 'director/e9cd35786422e87bd0571a4423bc947e50fe97e6'... Skipped [Package already compiled] (00:00:01) Compiling package 'nginx/2ec2f63293bf6f544e95969bf5e5242bc226a800'... Skipped [Package already compiled] (00:00:00) Compiling package 'registry/d81865cf0ad85fd79cb19aeb565bf622f2a17a83'... Skipped [Package already compiled] (00:00:00) Compiling package 'nats/63ae42eb73527625307ff522fb402832b407321d'... Skipped [Package already compiled] (00:00:00) Compiling package 'verify_multidigest/8fc5d654cebad7725c34bb08b3f60b912db7094a'... Skipped [Package already compiled] (00:00:00) Compiling package 'postgres-9.4/ded764a075ae7513d4718b7cf200642fdbf81ae4'... Skipped [Package already compiled] (00:00:00) Compiling package 'health_monitor/e9317b2ad349f019e69261558afa587537f06f25'... Skipped [Package already compiled] (00:00:00) Compiling package 'postgres/3b1089109c074984577a0bac1b38018d7a2890ef'... Skipped [Package already compiled] (00:00:00) Compiling package 'davcli/5f08f8d5ab3addd0e11171f739f072b107b30b8c'... Skipped [Package already compiled] (00:00:00) Updating instance 'bosh/0'... Finished (00:00:23) Waiting for instance 'bosh/0' to be running... Finished (00:01:09) Running the post-start scripts 'bosh/0'... Finished (00:00:00) Finished deploying (00:08:53) Stopping registry... Finished (00:00:00) Cleaning up rendered CPI jobs... Finished (00:00:00) Succeeded |
|||||||||||||||||||||||
|
|||||||||||||||||||||||
Re: Is Bosh is compatible with Openstack Ocata Version?
Hi Jan,
Thanks for your response. Let me start deployment with Ocata. I will surely update you. Thanks & Regards: Arpit Sharma |
|||||||||||||||||||||||
|
|||||||||||||||||||||||
Re: Is Bosh is compatible with Openstack Ocata Version?
Hi Dmitriy Kalinin,
Thanks for your response. Let me start deployment with Ocata. I will surely update you. Thanks & Regards: Arpit Sharma |
|||||||||||||||||||||||
|
|||||||||||||||||||||||
Re: Is Bosh is compatible with Openstack Ocata Version?
Jan von L?wenstein
Hi Arpit,
toggle quoted message
Show quoted text
We are not yet actively testing on Ocata but that is on the way. Until then I second Dmitriy, there is no reason to believe it wasn’t supported. Best Jan On 24.07.17, 17:34, "Dmitriy Kalinin" <dkalinin(a)pivotal.io> wrote:
no reasons yet to believe it isnt as far as i know. Sent from my iPhone > On Jul 24, 2017, at 7:56 AM, Arpit Sharma <arpitvipulsharma(a)gmail.com> wrote: > > Dear Team, > > Is bosh is compatilble with Openstack Ocata release? I am planning to deploy bosh on Ocata. > > Thanks & Regards: > Arpit Sharma |
|||||||||||||||||||||||
|
|||||||||||||||||||||||
Re: Is Bosh is compatible with Openstack Ocata Version?
Dmitriy Kalinin
no reasons yet to believe it isnt as far as i know.
toggle quoted message
Show quoted text
Sent from my iPhone On Jul 24, 2017, at 7:56 AM, Arpit Sharma <arpitvipulsharma(a)gmail.com> wrote: |
|||||||||||||||||||||||
|
|||||||||||||||||||||||
Is Bosh is compatible with Openstack Ocata Version?
Dear Team,
Is bosh is compatilble with Openstack Ocata release? I am planning to deploy bosh on Ocata. Thanks & Regards: Arpit Sharma |
|||||||||||||||||||||||
|
|||||||||||||||||||||||
Re: Option -N for bosh no longer available with bosh-cli v2?
Holger Oehm
Thanks, I'll do that. I opened an issue on github to request
toggle quoted message
Show quoted text
the feature: https://github.com/cloudfoundry/bosh-cli/issues/266 And I'll try out that workaround to run the bosh call in the background, too. On 07/13/2017 05:58 PM, Tyler Schultz wrote:
You may want to lobby Dmitriy to add the '--no-track' feature to the v2 |
|||||||||||||||||||||||
|