FAQ
While deploying a release, I got this error:

$ bosh deploy
Getting deployment properties from director...
Compiling deployment manifest...
Please review all changes carefully
Deploying `redis-dev.yml' to `micro' (type 'yes' to continue): yes

Director task 26

Preparing deployment
binding deployment (00:00:00)

binding releases (00:00:00)

binding existing deployment (00:00:00)

binding resource pools (00:00:00)

binding stemcells (00:00:00)

binding templates (00:00:00)

binding unallocated VMs (00:00:00)

binding instance networks (00:00:00)

Done 8/8 00:00:00


Reusing already compiled packages
copying compiled packages (00:00:00)

Done 1/1 00:00:00


Compiling packages
redis/0.1-dev: Timed out pinging to eddcaaf6-dc9a-4818-bb85-b85cd81ec775
after 300 seconds (00:05:19)
Error 1/1 00:05:19


Error 450002: Timed out pinging to eddcaaf6-dc9a-4818-bb85-b85cd81ec775
after 300 seconds

Task 26 error

If I ssh to the compilation vm while it's alive, I see there's an error on
the agent bootstraping process:

2012-07-08_22:59:04.88679 #[609] INFO: Starting agent 0.6.1...
2012-07-08_22:59:04.88687 #[609] INFO: Configuring agent...
2012-07-08_22:59:04.91139 #[609] INFO: Configuring instance
2012-07-08_22:59:05.37841 #[609] INFO: Loaded settings:
{"vm"=>{"name"=>"vm-ca13d745-4092-45e9-851f-2024a13bb4ab"},
"agent_id"=>"eddcaaf6-dc9a-4818-bb85-b85cd81ec775",
"networks"=>{"default"=>{"type
"=>"dynamic", "cloud_properties"=>{"security_groups"=>["default"]},
"default"=>["dns", "gateway"]}}, "disks"=>{"system"=>"/dev/vda",
"ephemeral"=>"/dev/vdb", "persistent"=>{}}, "env"=>{}}
2012-07-08_22:59:05.45158
/var/vcap/bosh/agent/lib/agent/bootstrap.rb:131:in `update_blobstore':
undefined method `[]' for nil:NilClass (NoMethodError)
2012-07-08_22:59:05.45164 from
/var/vcap/bosh/agent/lib/agent/bootstrap.rb:44:in `configure'
2012-07-08_22:59:05.45165 from /var/vcap/bosh/agent/lib/agent.rb:93:in
`start'
2012-07-08_22:59:05.45165 from /var/vcap/bosh/agent/lib/agent.rb:72:in `run'
2012-07-08_22:59:05.45165 from /var/vcap/bosh/agent/bin/agent:97:in `<main>'

The error is caused by the lack of blobstore properties that are read from
the registry. The question is: *who is responsible for providing these
properties? Are them stored at the director, or you must pass them at the
release config/final.yml file?*

---
blobstore:
provider: local
options:
blobstore_path: /tmp/blobstore

PS: Testing is done using the OpenStack CPI and a micro-bosh (not a fully
BOSH deployment).

TIA,
- Ferdy

Search Discussions

  • Martin Englund at Jul 10, 2012 at 5:49 pm

    On Sun, Jul 8, 2012 at 4:27 PM, ferdy wrote:

    The error is caused by the lack of blobstore properties that are read from
    the registry. The question is: who is responsible for providing these
    properties? Are them stored at the director, or you must pass them at the
    release config/final.yml file?
    The config/final.yml blobstore settings are just for building the
    release (i.e. source packages of final releases of what is in the
    bosh-release), what you are missing is the blobstore that is used in
    the bosh director to store its source packages and compiled packages.

    That config should have been setup when you deployed bosh.

    cheers,
    /Martin
    --
    Martin Englund, Staff Engineer, Cloud Foundry, VMware Inc.
    "The question is not if you are paranoid, it is if you are paranoid enough."
  • Ferdy at Jul 13, 2012 at 5:23 pm
    Thanks Martin, I'll check my bosh director config to see what's wrong.

    - Ferdy
    On Tuesday, July 10, 2012 7:49:36 PM UTC+2, Martin Englund wrote:
    On Sun, Jul 8, 2012 at 4:27 PM, ferdy wrote:

    The error is caused by the lack of blobstore properties that are read from
    the registry. The question is: who is responsible for providing these
    properties? Are them stored at the director, or you must pass them at the
    release config/final.yml file?
    The config/final.yml blobstore settings are just for building the
    release (i.e. source packages of final releases of what is in the
    bosh-release), what you are missing is the blobstore that is used in
    the bosh director to store its source packages and compiled packages.

    That config should have been setup when you deployed bosh.

    cheers,
    /Martin
    --
    Martin Englund, Staff Engineer, Cloud Foundry, VMware Inc.
    "The question is not if you are paranoid, it is if you are paranoid
    enough."

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
groupbosh-users @
postedJul 8, '12 at 11:27p
activeJul 13, '12 at 5:23p
posts3
users2

2 users in discussion

Ferdy: 2 posts Martin Englund: 1 post

People

Translate

site design / logo © 2022 Grokbase