領事boshrelease部署錯誤

我跟着他們的自述： https://github.com/cloudfoundry-community/consul-boshrelease/領事boshrelease部署錯誤

結果：

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

我試圖追查這Unknown CPI error，但無濟於事。

來源

2017-08-03 vcardillo

最後，問題是他們生成的清單文件中存在錯誤，他們的自述文件告訴您通過運行templates/make_manifest aws-ec2來生成。除了表單錯誤之外，正確的命令實際上只有templates/make_manifest aws（沒有「ec2」部分）。

無論如何，這裏是爲我部署了這個清單文件。請注意，Consul集羣實際上並沒有工作（儀表板上有500個錯誤），但是，這是另一篇文章的故事。尋找編輯$FOO項目，以取代你自己的。

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

來源

2017-08-11 19:07:55 vcardillo

我在將bosh部署到aws期間有同樣的錯誤信息。原因是我的bosh.yml清單中有一個錯誤。

相反

cloud_properties: {subnet: subnet-6b54e7f1}

我寫

cloud_properties: {subnet-6b54e7f1}

另一個原因是，我的實例類型爲M3。它必須是m4。我的更正後，此錯誤消息消失。

來源

2017-08-09 14:19:29

是啊......這是他們生成的清單文件中的錯誤。我將發佈解決方案。 – vcardillo

領事boshrelease部署錯誤

回答

相關問題