Hi Torben, Seth:
That happens to be the same version I'm using as well:
config.vm.provision "chef_client" do |chef|
chef.chef_server_url = ""
chef.validation_key_path = ""
chef.version = "11.16.4-1"
chef.binary_path = "/opt/chef/bin"
chef.delete_node = true
chef.delete
Hi William, Seth,
for what it's worth: I can confirm that setting `chef.version =
"11.16.4"` works with the :chef_solo provisioner. Have not tried with
:chef_client or :chef_zero though...
HTH,
Torben
On Sat, Dec 27, 2014 at 1:18 AM, William Jimenez wrote:
> Hi Seth
> Thanks for your respons
Hi Seth
Thanks for your response. I did destroy the box before trying the new
version of chef I'm afraid.
Regards,
William
On Thu, Dec 25, 2014 at 7:31 AM, Seth Vargo wrote:
> Hi William,
>
> I do not think the Chef omnibus installer gracefully handles downgrades.
> Can you try destroying the V
Hi William,
I do not think the Chef omnibus installer gracefully handles downgrades. Can
you try destroying the VM and making a new one with the correct version of Chef
installed?
Best,
Seth
> On Dec 24, 2014, at 5:49 PM, William Jimenez wrote:
>
> I'm using the chef-client provider for vagra
I'm using the chef-client provider for vagrant. When I don't specify the
version it defaults to installing the 12x chef-client, but I want an 11x
chef client, so I specified that with chef.version = "11.16.4-1". As soon
as I do that, vagrant fails to provision citing the following:
Vagrant coul
