Centos 6.7 I ran with debug and got no real additional information about the problem.
I was going to try it manually but not sure where to get an install package as doesn't appear to be a yum one? I am not sure what vagrant actually does when it tries to install chef as that would be a useful starter for the manual replication of the problem. I get the impression it is the install method that is the problem to azure but that is a 'stab in the dark' Regards Mark On Tuesday, 13 October 2015 09:00:44 UTC+1, Alvaro Miranda Aguilera wrote: > > what os is? > > Azure use a non-standard linux for most of the things. > > > VAGRANT_LOG=debug vagrant provision > > or > > VAGRANT_LOG=debug vagrant reload > > > will tell more info and show where it's failing. > > What happen if you install chef on your own? > > Alvaro > > On Tue, Oct 13, 2015 at 8:42 PM, <[email protected] <javascript:>> > wrote: > > Fairly new to vagrant but managed to fairly easy use virtual box and > create > > a Centos VM that is fully configured with some local apps via Chef. > > > > When I then tried to use Azure (After mastering the settings that in my > > opinion no-one has really documented properly what you do and don't need > and > > an idiots guide as to how to get them) I found that the chef install no > > longer worked. Message: > > > > "Vagrant attempted to execute the capability 'chef_install' > > on the detect guest OS 'linux', but the guest doesn't > > support that capability. This capability is required for your > > configuration of Vagrant. Please either reconfigure Vagrant to > > avoid this capability or fix the issue by creating the capability." > > > > Offending code in 'Vagrantfile' > > > > config.vm.provision "chef_apply" do |chef| > > chef.recipe = File.read("./SomeApp.rb") > > end > > > > I did think it was not correctly picking up the OS from Azure so tried > hard > > setting but to no avail. > > > > It is actually failing on the install off chef (chef solo I believe?). > > I have seen others have had a similar message related to other installs > and > > seen those described as bugs but nothing related to using chef against > an > > azure VM. > > > > Can anyone point me in the right direction please > > > > Regards > > > > Mark > > > > -- > > This mailing list is governed under the HashiCorp Community Guidelines - > > https://www.hashicorp.com/community-guidelines.html. Behavior in > violation > > of those guidelines may result in your removal from this mailing list. > > > > GitHub Issues: https://github.com/mitchellh/vagrant/issues > > IRC: #vagrant on Freenode > > --- > > 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] <javascript:>. > > To view this discussion on the web visit > > > https://groups.google.com/d/msgid/vagrant-up/7ec82acc-0b30-4864-bd68-2d48de6ca90f%40googlegroups.com. > > > > For more options, visit https://groups.google.com/d/optout. > -- This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list. GitHub Issues: https://github.com/mitchellh/vagrant/issues IRC: #vagrant on Freenode --- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/ce4bf7b6-b54a-4df8-b202-f614a044e83d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
