error generating deployment manifest from stub file


Sankeerth Sai
 

I was trying to deploy cloud foundry on vsphere. After creating stub file and running script to generate deployment manifest I ran in to this error.

error generating manifest: unresolved nodes:
(( .properties.cc.external_port )) in /home/ssanke001c/cf-release/templates/cf.yml jobs.[9].properties.route_registrar.routes.[0].port
(( .properties.nats.machines )) in /home/ssanke001c/cf-release/templates/cf.yml properties.etcd_metrics_server.nats.machines
(( .properties.cc.external_port )) in /home/ssanke001c/cf-release/templates/cf.yml meta.api_routes.[0].port

However I made a force deployment ignoring the above errors. As a result deployment failed.
Also, I had seen few more errors related to unresolved nodes (static ips). Because the cf.yml assumes two networks cf1,cf2. I have only cf1. I configured the cf-infrastructure-vsphere.yml and cf.yml from templates by removing jobs associated with cf2. I was able fix that issue. Can someone help me to get an understanding of how to deal with external port related issues and route registrar and how to configure them in my deployment manifest? thanks in advance.


Ronak Banka
 

Hi Sankeerth,

check for the missing properties in global property block, check if below
properties exists in your intermediate manifest or not.

properties:
cc:
external_port: ?? ( you can add this port as 9022 if it is not there)

nats:
machines: ?? ( this property will be populated from nats job IP's)

Thanks
Ronak

On Wed, Aug 17, 2016 at 5:08 AM, Sankeerth Sai <sankyrth4u(a)gmail.com> wrote:

I was trying to deploy cloud foundry on vsphere. After creating stub file
and running script to generate deployment manifest I ran in to this error.

error generating manifest: unresolved nodes:
(( .properties.cc.external_port )) in /home/ssanke001c/cf-release/templates/cf.yml
jobs.[9].properties.route_registrar.routes.[0].port
(( .properties.nats.machines )) in /home/ssanke001c/cf-release/templates/cf.yml
properties.etcd_metrics_server.nats.machines
(( .properties.cc.external_port )) in
/home/ssanke001c/cf-release/templates/cf.yml meta.api_routes.[0].port

However I made a force deployment ignoring the above errors. As a result
deployment failed.
Also, I had seen few more errors related to unresolved nodes (static
ips). Because the cf.yml assumes two networks cf1,cf2. I have only cf1. I
configured the cf-infrastructure-vsphere.yml and cf.yml from templates by
removing jobs associated with cf2. I was able fix that issue. Can someone
help me to get an understanding of how to deal with external port related
issues and route registrar and how to configure them in my deployment
manifest? thanks in advance.


Sankeerth Sai
 

Thanks Ronak. It worked. I have declared those properties and deployment manifest got generated.
However when I tried to deploy most of the vms got deployed but consul failed resulting in deployment error
Director task 302
Deprecation: Ignoring cloud config. Manifest contains 'networks' section.

Started preparing deployment > Preparing deployment. Done (00:00:01)

Started preparing package compilation > Finding packages to compile. Done (00:00:00)

Started updating job consul_z1 > consul_z1/0 (xxxxxxxx) (canary). Failed: 'consul_z1/0 (xxxxxx)' is not running after update. Review logs for failed jobs: consul_agent (00:10:36)

Error 400007: 'consul_z1/0 (xxx)' is not running after update. Review logs for failed jobs: consul_agent

The logs under /var/vcap/sys/log indicate "error parsing any certificates"...I checked many times the consul certificates t but couldn't figure out the issue.......I used certstarp to generate self signed certs with an encrypted key...Do I need to declare any additional properties in consul for my deployment manifest before doing bosh deploy? or is it purely syntax related issue?


Amit Kumar Gupta
 

Hi Sankeerth,

Can you open an issue on
https://github.com/cloudfoundry-incubator/consul-release/issues? It's
helpful if you can mention what version of cf-release you're using, and if
you can include a link to your manifest file, with any sensitive data
redacted. Chances are the certificates you've put in for Consul are
malformed, or the manifest YAML where you've actually declared the certs is
syntactically incorrect.

Best,
Amit

On Wed, Aug 17, 2016 at 6:58 PM, Sankeerth Sai <sankyrth4u(a)gmail.com> wrote:

Thanks Ronak. It worked. I have declared those properties and deployment
manifest got generated.
However when I tried to deploy most of the vms got deployed but consul
failed resulting in deployment error
Director task 302
Deprecation: Ignoring cloud config. Manifest contains 'networks' section.

Started preparing deployment > Preparing deployment. Done (00:00:01)

Started preparing package compilation > Finding packages to compile.
Done (00:00:00)

Started updating job consul_z1 > consul_z1/0 (xxxxxxxx) (canary).
Failed: 'consul_z1/0 (xxxxxx)' is not running after update. Review logs for
failed jobs: consul_agent (00:10:36)

Error 400007: 'consul_z1/0 (xxx)' is not running after update. Review logs
for failed jobs: consul_agent

The logs under /var/vcap/sys/log indicate "error parsing any
certificates"...I checked many times the consul certificates t but couldn't
figure out the issue.......I used certstarp to generate self signed certs
with an encrypted key...Do I need to declare any additional properties in
consul for my deployment manifest before doing bosh deploy? or is it purely
syntax related issue?