I'm using vagrant-libvirt and chef_client. on "vagrant up" the chef_client
works fine with no errors.
On "vagrant destroy" chef_client does not seem to kick in at all. With
export VAGRANT_LOG=info on there doesn't seem to be any indication that
chef_client is trying to do anything when "vagrant destroy" is run. Is this
a bug or do I have something configured incorrectly.
I've made a patch with vagrant-triggers to remove the client and node from
chef. Which is not ideal, but works.
config.vm.provision "chef_client" do |chef|
chef.delete_client = true
chef.delete_node = true
chef.chef_server_url = "https://chef.<myserver>/"
chef.validation_key_path = "~/.chef/chef-validator.pem"
end
INFO global: Vagrant version: 1.7.2
INFO global: Ruby version: 2.0.0
INFO global: RubyGems version: 2.0.14
INFO global: - vagrant-libvirt = 0.0.29
--
You received this message because you are subscribed to the Google Groups
"Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
