Bosh-init - create_vm, connection refused


William C Penrod
 

This is working now. Thanks for your help on this.

On Wed, Nov 11, 2015 at 7:55 PM, William C Penrod <wcpenrod(a)gmail.com>
wrote:

bosh-init -v
version 0.0.80-a62aad7-2015-10-28T01:52:30Z


William C Penrod
 

bosh-init -v
version 0.0.80-a62aad7-2015-10-28T01:52:30Z


William C Penrod
 

I was missing the ssh properties under the cloud_provider. Its interesting as it seems to have dropped back to the registry without the ssh info.

I added that in and it created the vm ok. The bosh agent is running but it did not create any of the other jobs. I'll dig in and see whats going on there.


Dmitriy Kalinin
 

are you using latest version of bosh-init? bosh.io/docs/install-bosh-init.html

Sent from my iPhone

On Nov 11, 2015, at 6:07 PM, William C Penrod <wcpenrod(a)gmail.com> wrote:

That is correct. If I don't put the registry info under cloud_provider, I get the following error:

Command 'deploy' failed:
Installing CPI:
Rendering and uploading Jobs:
Rendering job templates for installation:
Rendering templates for job 'aws_cpi/67491119351881e35f3130231ff7089e7a13e83b':
Rendering template src: cpi.json.erb, dst: config/cpi.json:
Rendering template src: /home/ec2-user/.bosh_init/installations/3c576845-76d5-4467-505f-e2c3af6a2540/tmp/bosh-init-release665047630/extracted_jobs/aws_cpi/templates/cpi.json.erb, dst: /home/ec2-user/.bosh_init/installations/3c576845-76d5-4467-505f-e2c3af6a2540/tmp/rendered-jobs897206626/config/cpi.json:
Running ruby to render templates:
Running command: 'ruby /home/ec2-user/.bosh_init/installations/3c576845-76d5-4467-505f-e2c3af6a2540/tmp/erb-renderer761234148/erb-render.rb /home/ec2-user/.bosh_init/installations/3c576845-76d5-4467-505f-e2c3af6a2540/tmp/erb-renderer761234148/erb-context.json /home/ec2-user/.bosh_init/installations/3c576845-76d5-4467-505f-e2c3af6a2540/tmp/bosh-init-release665047630/extracted_jobs/aws_cpi/templates/cpi.json.erb /home/ec2-user/.bosh_init/installations/3c576845-76d5-4467-505f-e2c3af6a2540/tmp/rendered-jobs897206626/config/cpi.json', stdout: '', stderr: '/home/ec2-user/.bosh_init/installations/3c576845-76d5-4467-505f-e2c3af6a2540/tmp/erb-renderer761234148/erb-render.rb:180:in `rescue in render': Error filling in template '/home/ec2-user/.bosh_init/installations/3c576845-76d5-4467-505f-e2c3af6a2540/tmp/bosh-init-release665047630/extracted_jobs/aws_cpi/templates/cpi.json.erb' for aws_cpi/0 (line 17: #<TemplateEvaluationContext::UnknownProperty: Can't find property '
registry
.username'>) (RuntimeError)
from /home/ec2-user/.bosh_init/installations/3c576845-76d5-4467-505f-e2c3af6a2540/tmp/erb-renderer761234148/erb-render.rb:166:in `render'
from /home/ec2-user/.bosh_init/installations/3c576845-76d5-4467-505f-e2c3af6a2540/tmp/erb-renderer761234148/erb-render.rb:191:in `<main>'
':
exit status 1


William C Penrod
 

That is correct. If I don't put the registry info under cloud_provider, I get the following error:

Command 'deploy' failed:
Installing CPI:
Rendering and uploading Jobs:
Rendering job templates for installation:
Rendering templates for job 'aws_cpi/67491119351881e35f3130231ff7089e7a13e83b':
Rendering template src: cpi.json.erb, dst: config/cpi.json:
Rendering template src: /home/ec2-user/.bosh_init/installations/3c576845-76d5-4467-505f-e2c3af6a2540/tmp/bosh-init-release665047630/extracted_jobs/aws_cpi/templates/cpi.json.erb, dst: /home/ec2-user/.bosh_init/installations/3c576845-76d5-4467-505f-e2c3af6a2540/tmp/rendered-jobs897206626/config/cpi.json:
Running ruby to render templates:
Running command: 'ruby /home/ec2-user/.bosh_init/installations/3c576845-76d5-4467-505f-e2c3af6a2540/tmp/erb-renderer761234148/erb-render.rb /home/ec2-user/.bosh_init/installations/3c576845-76d5-4467-505f-e2c3af6a2540/tmp/erb-renderer761234148/erb-context.json /home/ec2-user/.bosh_init/installations/3c576845-76d5-4467-505f-e2c3af6a2540/tmp/bosh-init-release665047630/extracted_jobs/aws_cpi/templates/cpi.json.erb /home/ec2-user/.bosh_init/installations/3c576845-76d5-4467-505f-e2c3af6a2540/tmp/rendered-jobs897206626/config/cpi.json', stdout: '', stderr: '/home/ec2-user/.bosh_init/installations/3c576845-76d5-4467-505f-e2c3af6a2540/tmp/erb-renderer761234148/erb-render.rb:180:in `rescue in render': Error filling in template '/home/ec2-user/.bosh_init/installations/3c576845-76d5-4467-505f-e2c3af6a2540/tmp/bosh-init-release665047630/extracted_jobs/aws_cpi/templates/cpi.json.erb' for aws_cpi/0 (line 17: #<TemplateEvaluationContext::UnknownProperty: Can't find property 'registry
.username'>) (RuntimeError)
from /home/ec2-user/.bosh_init/installations/3c576845-76d5-4467-505f-e2c3af6a2540/tmp/erb-renderer761234148/erb-render.rb:166:in `render'
from /home/ec2-user/.bosh_init/installations/3c576845-76d5-4467-505f-e2c3af6a2540/tmp/erb-renderer761234148/erb-render.rb:191:in `<main>'
':
exit status 1


Dmitriy Kalinin
 

It seems that your manifest is specifying for the CPI to connect to 25777
for registry. You probably added registry properties under cloud_provider
section. See example manifest: http://bosh.io/docs/init-aws.html

On Wed, Nov 11, 2015 at 3:41 PM, William C Penrod <wcpenrod(a)gmail.com>
wrote:

I'm stuck on deploying a director_vm with bosh-init into aws.

Command 'deploy' failed:
Deploying:
Creating instance 'bosh/0':
Creating VM:
Creating vm with stemcell cid 'ami-1b275f7e light':
CPI 'create_vm' method responded with error:
CmdError{"type":"Unknown","message":"Connection refused - connect(2) for
\"10.0.0.6\" port 25777 (http://10.0.0.6:25777)","ok_to_retry":false}

The security groups are open to all inbound traffic for testing. When the
vm is created, as soon as services are available, it shuts down. I've tried
to ssh to the box but as soon as it accepts an ssh connection, the vm shuts
down and I get the error message.

Is there a property I can set to extend how long bosh-init waits for the
connection to be established to give me some time to figure out what is
happening on the vm?


William C Penrod
 

I'm stuck on deploying a director_vm with bosh-init into aws.

Command 'deploy' failed:
Deploying:
Creating instance 'bosh/0':
Creating VM:
Creating vm with stemcell cid 'ami-1b275f7e light':
CPI 'create_vm' method responded with error: CmdError{"type":"Unknown","message":"Connection refused - connect(2) for \"10.0.0.6\" port 25777 (http://10.0.0.6:25777)","ok_to_retry":false}

The security groups are open to all inbound traffic for testing. When the vm is created, as soon as services are available, it shuts down. I've tried to ssh to the box but as soon as it accepts an ssh connection, the vm shuts down and I get the error message.

Is there a property I can set to extend how long bosh-init waits for the connection to be established to give me some time to figure out what is happening on the vm?