consul-boshrelease deployment errors

Question

I followed their readme: https://github.com/cloudfoundry-community/consul-boshrelease/

Result:

Deploying
---------

Director task 1990
Deprecation: Ignoring cloud config. Manifest contains 'networks' section.

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

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

  Started compiling packages
  Started compiling packages > envconsul/90d4cc3b4e290c3833cf5e32d0b5c99f4a63c0be
  Started compiling packages > consul-template/561a4a5d99c375822876d5482ed24f790a0e216b
  Started compiling packages > consul/30f12d1e70d89f28b34a433d2b885a03ae41adae
   Failed compiling packages > consul-template/561a4a5d99c375822876d5482ed24f790a0e216b: Unknown CPI error 'InvalidCall' with message 'Arguments are not correct, details: 'expected params[:filters][0][:values][0] to be a String, got value nil (class: NilClass) instead.'' in 'create_vm' CPI method (00:00:12)
   Failed compiling packages > envconsul/90d4cc3b4e290c3833cf5e32d0b5c99f4a63c0be: Unknown CPI error 'InvalidCall' with message 'Arguments are not correct, details: 'expected params[:filters][0][:values][0] to be a String, got value nil (class: NilClass) instead.'' in 'create_vm' CPI method (00:00:12)
   Failed compiling packages > consul/30f12d1e70d89f28b34a433d2b885a03ae41adae: Unknown CPI error 'InvalidCall' with message 'Arguments are not correct, details: 'expected params[:filters][0][:values][0] to be a String, got value nil (class: NilClass) instead.'' in 'create_vm' CPI method (00:00:12)
   Failed compiling packages (00:00:12)

Error 100: Unknown CPI error 'InvalidCall' with message 'Arguments are not correct, details: 'expected params[:filters][0][:values][0] to be a String, got value nil (class: NilClass) instead.'' in 'create_vm' CPI method

Task 1990 error

I've tried to track down this Unknown CPI error, to no avail.

score 0 · Answer 1 · answered Aug 09 '17 at 14:19

0

I had the same error message during I was deploying bosh to aws. The reason was a mistake in my bosh.yml manifest.

Instead

cloud_properties: {subnet: subnet-6b54e7f1}

I was write

cloud_properties: {subnet-6b54e7f1}

The other reason was that my instance type was m3. It has to be m4. After my corrections this error message disappeared.

answered Aug 09 '17 at 14:19

Abs.end

1
3

Yeah... it was errors in their generated manifest file. I'm going to post the solution. – vcardillo Aug 11 '17 at 19:02

score 0 · Accepted Answer · answered Aug 11 '17 at 19:07

In the end, the problem was errors in their generated manifest file, that their readme tells you to generate by running templates/make_manifest aws-ec2. Aside from the manifest being wrong, the proper command there is actually just templates/make_manifest aws (without the "ec2" portion).

Anyways, here's the manifest file that got this deployed for me. Mind you, the Consul cluster wasn't actually working (500 errors on the dashboard), but, that's a story for another post. Look for the redacted $FOO items, to replace with your own.

compilation:
  cloud_properties:
    instance_type: m3.medium
    availability_zone: us-east-1d
  network: consul1
  reuse_compilation_vms: true
  workers: 6
director_uuid: $YOUR_ID
jobs:
- instances: 3
  name: consul
  networks:
  - name: consul1
  persistent_disk: 4096
  properties:
    consul:
      join_host: 0.consul-z1.consul1.consul-aws.microbosh
      services:
        example: {}
    networks:
      apps: consul1
  resource_pool: small_z1
  templates:
  - consumes:
      consul_servers:
        from: consul_leaders
    name: consul
    provides:
      consul_servers:
        as: consul_leaders
    release: consul
  update:
    canaries: 0
    max_in_flight: 50
name: consul-aws
networks:
- cloud_properties: {}
  name: floating
  type: vip
- cloud_properties:
    subnet: $YOUR_SUBNET
    security_groups:
    - default
    availability_zone: us-east-1d
  name: consul1
  type: dynamic
properties: {}
releases:
- name: consul
  version: latest
resource_pools:
- cloud_properties:
    instance_type: m3.medium
    availability_zone: us-east-1d
  name: small_z1
  network: consul1
  stemcell:
    name: bosh-aws-xen-hvm-ubuntu-trusty-go_agent
    version: latest
update:
  canaries: 0
  canary_watch_time: 1000-60000
  max_in_flight: 50
  serial: true
  update_watch_time: 1000-60000

consul-boshrelease deployment errors

2 Answers2