search

schubergphilis / vagrant-chef-zero

Vagrant Plugin for Chef Zero
Apache License 2.0
91 stars 41 forks source link

"vagrant provision" and "vagrant reload" cause "address in use" errors #20

Closed eherot closed 11 years ago

eherot commented 11 years ago

Would be great if these commands would actually work so that a complete teardown of the instance is not required every time I fix a cookbook bug.

andrewgross commented 11 years ago

Thanks for reporting, will investigate.

bytheway commented 11 years ago

+1. This is a killer behavior when you are trying to validate behavior quickly while updating the cookbook.

memelet commented 11 years ago

Yes, this is a show stopper. Does anybody use chef-zero with vagrant but from the command instead via the plugin?

andrewgross commented 11 years ago

Will put some time into this over the weekend. Thanks for corroborating.

andrewgross commented 11 years ago

Fixed in 0.4.1. The 0.4.0 release attempted to use the Chef-Zero gem inside of Vagrant, instead of calling out to the binary. The problem arose when the server died at the end of the Vagrant run, as the ports were not freed. I have reverted back to calling the binary directly.