Chef install not working with azure provider

62 views
Skip to first unread message

marka...@gmail.com

unread,
Oct 13, 2015, 3:42:55 AM10/13/15
to Vagrant
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 

Alvaro Miranda Aguilera

unread,
Oct 13, 2015, 4:00:44 AM10/13/15
to vagra...@googlegroups.com
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
> --
> 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 vagrant-up+...@googlegroups.com.
> 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.

marka...@gmail.com

unread,
Oct 13, 2015, 4:35:06 AM10/13/15
to Vagrant
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

marka...@gmail.com

unread,
Oct 13, 2015, 5:41:51 AM10/13/15
to Vagrant
Basically I have circumvented this problem by pre installing chef myself with the command:

curl -L https://www.opscode.com/chef/install.sh | bash

Would still be interested to know what Vagrant is trying to do

Thanks

Mark

Alvaro Miranda Aguilera

unread,
Oct 13, 2015, 5:46:40 AM10/13/15
to vagra...@googlegroups.com

marka...@gmail.com

unread,
Oct 13, 2015, 7:08:22 AM10/13/15
to Vagrant
Alvaro,

The debug adds nothing at all extra. Just repeats the 4 lines of error in the original post.
As you properly were, I was at the least expecting to see command it was trying to run.

Regards

Mark


Seth Vargo

unread,
Oct 13, 2015, 10:24:42 AM10/13/15
to vagra...@googlegroups.com
Hi Mark,

I know you think that the debug logs are not helpful, but we need them to diagnose your issue. There should be a few hundreds lines of debug output, and those help us in diagnosing the issue. The logs also tell us important things like what version of Vagrant you are running, the list of installed plugins, etc. Without those logs, we are shooting in the dark.

Best,
Seth

--
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 vagrant-up+...@googlegroups.com.
Reply all
Reply to author
Forward
0 new messages