bosh deployments - 500s
drnic opened this issue · comments
$ bosh deployments
HTTP 500:
Inside vagrant:
$ tail -f /var/log/director/current
...
2014-01-29_21:28:53.57858 E, [2014-01-29T13:28:53.577548 #965] [0xfe1078] ERROR -- : NoMethodError - undefined method `name' for #<Bosh::Director::Models::Deployment:0x00000003f59940>:
2014-01-29_21:28:53.57860 /opt/rbenv/versions/1.9.3-p484/lib/ruby/gems/1.9.1/gems/bosh-director-1.5.0.pre.1657/lib/bosh/director/api/controllers/deployments_controller.rb:140:in `block (2 levels) in <class:DeploymentsController>'
We have created an issue in Pivotal Tracker to manage this. You can view the current status of your issue at: http://www.pivotaltracker.com/story/show/64778030
This maps to this line in warden-cpi branch:
This is resolved when I kill the director process and it is restarted. Which I assume means that it loads in the schema correctly and thus Bosh::Director::Models::Deployment model now has an #name getter.
Could it be caused by a race condition - the director is loaded & running before the DB is migrated?
From outside vagrant, kill the director with:
vagrant ssh -c "ps ax | grep 'director.yml' | head -n 1 | awk '{print \$1}' | xargs sudo kill"
Was this a fresh vagrant up?
Yep. Been happening for a while. I don't think all the time (hence a guess at a race condition). Unsure if it predates the new vagrant box.
On Wed, Jan 29, 2014 at 2:22 PM, Matthew Kocher notifications@github.com
wrote:
Was this a fresh
vagrant up?Reply to this email directly or view it on GitHub:
#82 (comment)
@drnic,
Is this still a problem? The ticket's pretty old at this point.