Could not find properties.loggregator.incoming_port.

[brea...@gmail.com]

I've been following the instructions for deploying CF on AWS, and I've hit up on this error.

Release rebased
Creating deployment manifest cf-aws.yml
Deployment set to `/home/vagrant/cf/cf-aws.yml'
Could not find properties.loggregator.incoming_port.
'/tmp/cf-release/templates/cf-aws-template.yml.erb' has it but '/home/vagrant/cf/cf-aws.yml' does not.
Could not find properties.
'/tmp/cf-release/templates/cf-aws-template.yml.erb' has it but '/home/vagrant/cf/cf-aws.yml' does not.
/home/vagrant/.rbenv/versions/1.9.3-p448/lib/ruby/gems/1.9.1/gems/bosh_cli-1.5.0.pre.1090/lib/cli/commands/biff.rb:172:in `delete_all_except': undefined method `each_index' for nil:NilClass (NoMethodError)
 from /home/vagrant/.rbenv/versions/1.9.3-p448/lib/ruby/gems/1.9.1/gems/bosh_cli-1.5.0.pre.1090/lib/cli/commands/biff.rb:201:in `print_the_template_path'
 from /home/vagrant/.rbenv/versions/1.9.3-p448/lib/ruby/gems/1.9.1/gems/bosh_cli-1.5.0.pre.1090/lib/cli/commands/biff.rb:141:in `block in find'
 from /home/vagrant/.rbenv/versions/1.9.3-p448/lib/ruby/gems/1.9.1/gems/bosh_cli-1.5.0.pre.1090/lib/cli/commands/biff.rb:126:in `each'
 from /home/vagrant/.rbenv/versions/1.9.3-p448/lib/ruby/gems/1.9.1/gems/bosh_cli-1.5.0.pre.1090/lib/cli/commands/biff.rb:126:in `find'
 from (erb):141:in `biff'
 from /home/vagrant/.rbenv/versions/1.9.3-p448/lib/ruby/1.9.1/erb.rb:835:in `eval'
 from /home/vagrant/.rbenv/versions/1.9.3-p448/lib/ruby/1.9.1/erb.rb:835:in `block in result'
 from /home/vagrant/.rbenv/versions/1.9.3-p448/lib/ruby/1.9.1/erb.rb:833:in `call'
 from /home/vagrant/.rbenv/versions/1.9.3-p448/lib/ruby/1.9.1/erb.rb:833:in `result'
 from /home/vagrant/.rbenv/versions/1.9.3-p448/lib/ruby/gems/1.9.1/gems/bosh_cli-1.5.0.pre.1090/lib/cli/commands/biff.rb:24:in `biff'
 from /home/vagrant/.rbenv/versions/1.9.3-p448/lib/ruby/gems/1.9.1/gems/bosh_cli-1.5.0.pre.1090/lib/cli/command_handler.rb:57:in `run'
 from /home/vagrant/.rbenv/versions/1.9.3-p448/lib/ruby/gems/1.9.1/gems/bosh_cli-1.5.0.pre.1090/lib/cli/runner.rb:59:in `run'
 from /home/vagrant/.rbenv/versions/1.9.3-p448/lib/ruby/gems/1.9.1/gems/bosh_cli-1.5.0.pre.1090/lib/cli/runner.rb:18:in `run'
 from /home/vagrant/.rbenv/versions/1.9.3-p448/lib/ruby/gems/1.9.1/gems/bosh_cli-1.5.0.pre.1090/bin/bosh:7:in `<top (required)>'
 from /home/vagrant/.rbenv/versions/1.9.3-p448/bin/bosh:23:in `load'
 from /home/vagrant/.rbenv/versions/1.9.3-p448/bin/bosh:23:in `<main>'
Time of crash:
 2013-10-13 04:45:13 +0000
 
RuntimeError: Failed to run: bosh -n diff /tmp/cf-release/templates/cf-aws-template.yml.erb
 
bootstrap-cf-plugin-ee90e91d0309/lib/bootstrap-cf-plugin/infrastructure/aws.rb:87:in `sh'
bootstrap-cf-plugin-ee90e91d0309/lib/bootstrap-cf-plugin/infrastructure/aws.rb:38:in `deploy_release'
bootstrap-cf-plugin-ee90e91d0309/lib/bootstrap-cf-plugin/infrastructure/aws.rb:9:in `bootstrap'
bootstrap-cf-plugin-ee90e91d0309/lib/bootstrap-cf-plugin/plugin.rb:15:in `bootstrap'
mothership-0.5.1/lib/mothership/base.rb:66:in `run'
mothership-0.5.1/lib/mothership/command.rb:72:in `block in invoke'
mothership-0.5.1/lib/mothership/command.rb:86:in `instance_exec'
mothership-0.5.1/lib/mothership/command.rb:86:in `invoke'
mothership-0.5.1/lib/mothership/base.rb:55:in `execute'
cf-5.2.2/lib/cf/cli.rb:195:in `block (2 levels) in execute'
cf-5.2.2/lib/cf/cli.rb:202:in `save_token_if_it_changes'
cf-5.2.2/lib/cf/cli.rb:194:in `block in execute'
cf-5.2.2/lib/cf/cli.rb:123:in `wrap_errors'
cf-5.2.2/lib/cf/cli.rb:190:in `execute'
mothership-0.5.1/lib/mothership.rb:45:in `start'
cf-5.2.2/bin/cf:18:in `<top (required)>'
/home/vagrant/.rbenv/versions/1.9.3-p448/bin/cf:23:in `load'
/home/vagrant/.rbenv/versions/1.9.3-p448/bin/cf:23:in `<main>'

The requested info to provide when asking for help:

bosh gem versions:

vagrant@precise64:~/cf$ gem list bosh                    


*** LOCAL GEMS ***


bosh (1.3.0)
bosh-registry (1.5.0.pre.1090)
bosh-stemcell (1.5.0.pre.1090)
bosh_aws_cpi (1.5.0.pre.1090)
bosh_cli (1.5.0.pre.1090)
bosh_cli_plugin_aws (1.5.0.pre.1090)
bosh_cli_plugin_micro (1.5.0.pre.1090)
bosh_common (1.5.0.pre.1090)
bosh_cpi (1.5.0.pre.1090)
bosh_openstack_cpi (1.5.0.pre.1090)
bosh_vcloud_cpi (0.4.9)
bosh_vsphere_cpi (1.5.0.pre.1090)

bosh director info

vagrant@precise64:~/cf$ bosh status
Config
             /home/vagrant/.bosh_config


Director
  Name       micro-cftest
  URL        https://54.208.225.13:25555
  Version    1.5.0.pre.1100 (release:a5984f12 bosh:a5984f12)
  User       bb
  UUID       dd0c278b-5464-46a8-8f4d-2d47b83a88f0
  CPI        aws
  dns        enabled (domain_name: microbosh)
  compiled_package_cache disabled
  snapshots  enabled


Deployment
  Manifest   /home/vagrant/cf/cf-aws.yml

stemcell: latest as of this morning

cf-release: 144.1-dev

deployment manifest:

---
name: <redacted>
director_uuid: <redacted>
releases:
- name: cf-release
  version: latest
networks:
- name: cf1
  type: manual
  subnets:
  - range: 10.10.16.0/24
    name: default_unused
    reserved:
    - 10.10.16.2 - 10.10.16.9
    static:
    - 10.10.16.10 - 10.10.16.255
    gateway: 10.10.16.1
    dns:
    - 10.10.0.2
- name: services1
  type: manual
  subnets:
  - range: 10.10.32.0/20
    name: default_unused
    reserved:
    - 10.10.32.2 - 10.10.32.9
    static:
    - 10.10.32.10 - 10.10.32.255
    gateway: 10.10.32.1
    dns:
    - 10.10.0.2
properties:
  domain: <redacted>
  template_only:
    aws:
      access_key_id: <redacted>
      secret_access_key: <redacted>
      availability_zone: us-east-1d
      subnet_ids:
        cf1: <redacted>
        services1: <redacted>
  ccdb: &22639500
    db_scheme: mysql
    roles:
    - tag: admin
      name: <redacted>
      password: <redacted>
    databases:
    - tag: cc
      name: ccdb
    address: <redacted>
    port: 3306
  uaadb:
    db_scheme: mysql
    roles:
    - tag: admin
      name: <redacted>
      password: <redacted>
    databases:
    - tag: uaa
      name: uaadb
    address: <redacted>
    port: 3306
  uaa:
    jwt:
      signing_key: generate this with 'openssl genrsa -out signing_key.pem 2048'
      verification_key: generate this with 'openssl rsa -pubout -in signing_key.pem
        -out verification_key.pem'
    cc:
      client_secret: <redacted>
    admin:
      client_secret: <redacted>
    batch:
      username: <redacted>
      password: <redacted>
    clients:
      login:
        secret: <redacted>
      portal:
        secret: your-client-secret-for-portal
      billing:
        secret: your-client-secret-for-billing
      app-direct:
        secret: your-client-secret-for-app-direct
      support-services:
        secret: <redacted>
      servicesmgmt:
        secret: <redacted>
    scim:
      users:
      - admin|<redacted>|scim.write,scim.read,openid,cloud_controller.admin
      - services|<redacted>|scim.write,scim.read,openid,cloud_controller.admin
  nats:
    user: <redacted>
    password: <redacted>
  cc:
    bulk_api_password: <redacted>
    staging_upload_user: <redacted>
    staging_upload_password: <redacted>
    db_encryption_key: <redacted>
  router:
    status:
      user: <redacted>
      password: <redacted>
  syslog_aggregator:
    log_email:
      from_email: youraccount@example.com
      from_password: y0urp4ssword
  marketplace_gateway:
    service_auth_tokens:
      mongolab-dev_objectlabs: insert auth token here
      sendgrid-dev_sendgrid: insert auth token here
      sendgrid_sendgrid: insert auth token here
      redistogo-dev_redistogo: insert auth token here
      dummy_dummy: insert auth token here
      dummy-dev_dummy: insert auth token here
      newrelic_newrelic: insert auth token here
      urbanairship_urbanairship: insert auth token here
      treasuredata_treasuredata: insert auth token here
      blazemeter_blazemeter: insert auth token here
      searchify_searchify: insert auth token here
      cloudamqp-dev_cloudamqp: insert auth token here
    appdirect:
      key: insert app direct key
      secret: insert app direct secret
  mysql_gateway:
    token: <redacted>
  ccdb_ng: *22639500

The error occurs after successfully running `bosh aws create` and `bosh aws bootstrap micro`. It seems to fail immediately after completing Director Task 2. For some reason, it doesn't seem to be generating cf-aws.yml properly. I dropped the full output in a gist, in case it may be helpful in some way.

I've been able to deploy a single VM instance via vagrant-aws without issue, but now I'd like to give a full install of CF v2 on an AWS VPC a try, and this seems to be the only method available at the moment.

I'm going to continue to do some digging into BOSH of course, to see if I can work this out, and I'll update if I am able to do so. Any help tracking this down would be greatly appreciated.

[James Bayer]

the message indicators the root problem is that this is missing in your manifest, which the template is looking for:

properties.loggregator.incoming_port

perhaps you could just change the template to hard-code it to 80 or something like for the 3 places where it is getting referenced. loggregator is not quite finished yet and it's clear that the rough edges are still there in various parts of the system.

https://github.com/cloudfoundry/cf-release/blob/master/templates/cf-aws-template.yml.erb#L141

another option could be to edit the spec file here and put a default value in like 80.

https://github.com/cloudfoundry/cf-release/blob/master/jobs/loggregator/spec#L29-L30

once you make changes you'll have to create a new release and upload it. i haven't done the aws deployment for a long time, so i'm not sure if the aws scripts support that or not.

To unsubscribe from this group and stop receiving emails from it, send an email to bosh-users+...@cloudfoundry.org.

--

Thank you,

James Bayer

[Benedict Dodd]

I'm having exactly the same issue. Did anyone find a solution for it?

Thanks, Ben

[brea...@gmail.com]

I was side-tracked with more pressing concerns, but now that I'm back on this, I went with James' first solution, and did a simple sed to the existing cf-release left in the /tmp/ directory, immediately after hitting that error:

     

sed -i "s/<%= find('properties.loggregator.incoming_port') %>/80/g" /tmp/cf-release/templates/cf-aws-template.yml.erb

I re-ran:

bundle exec cf bootstrap aws

and it continued past that particular sticking point. Whether or not the fix might break something else down the line remains to be seen. I'll update if so.