Re: CF deployment on BOSH-lite


Natalie Bennett
 

You should 100% be using cf-deployment for local development at this point.
Release Integration is now working with Pivotal CloudOps to transition
Pivotal's production CF instance to cf-deployment.

Once there's a running production instance of cf-deployment, RelInt will
begin the process of deprecating cf-release. If you can avoid transitioning
yourself, or learning cf-r's manifest generation, you should.

Exactly what's going on with consul depends on why Bosh lite crashed. I
personally wouldn't spend much time debugging it since consul is also in
the process of being removed.

A couple of possible steps for the consul problem:

1. That error output looks like a problem with certs, so those certs might
just be wrong. You won't have that problem with cf-d since it generates its
own certs.

2. When in doubt and not in production, scale consul down to 1, delete its
data directory (I think /var/vcap/store but I'd expect the consul release
repo to have instructions) and scale back up

3. Though what I'd do is tear the whole thing down and start over.

- Natalie
On Thu, Aug 10, 2017 at 7:53 AM Subhankar Chattopadhyay <subho.atg(a)gmail.com>
wrote:

Hi,

I used to deploy CF using the
cf-release(https://github.com/cloudfoundry/cf-release) and following
the steps mentioned in
http://docs.cloudfoundry.org/deploying/boshlite/create_a_manifest.html.
It was working fine till my bosh-lite crashed and when I tried to re
install, consul_z1 was not running and I got the following error
inside the log

error during stop: dial tcp [::1]:8400: getsockopt: connection refused
error during start: timeout exceeded: "rpc error: failed to get conn:
x509: certificate has expired or is not yet valid"
2017/08/09 04:23:24 [ERR] agent.client: Failed to decode response header:
EOF
2017/08/09 04:23:24 [ERR] agent.client: Failed to decode response header:
EOF
error during start: timeout exceeded: "rpc error: failed to get conn:
x509: certificate has expired or is not yet valid"
2017/08/09 04:24:26 [ERR] agent.client: Failed to decode response header:
EOF
2017/08/09 04:24:26 [ERR] agent.client: Failed to decode response header:
EOF
error during start: timeout exceeded: "rpc error: failed to get conn:
x509: certificate has expired or is not yet valid"


Am I missing some steps here? Should I deploy with new certificates ?

I then deployed bosh and cf using
bosh-deployment(https://github.com/cloudfoundry/bosh-deployment) and
cf-deployment(https://github.com/cloudfoundry/cf-deployment). It
worked perfectly.

I am wondering if cf-deployment is the way to go for local bosh-lite
development or I should try with cf-release? Can someone help me with
this?



Regards,
Subhankar Chattopadhyay
Bangalore, India

Join cf-dev@lists.cloudfoundry.org to automatically receive all group messages.