I wanted to be familiar with working with chef-server so after playing with
chef-solo I headed to the official tutorials. So I have successfully
finished the first and second tutorial but I have been struggling for a
while now on the Learn to manage a basic web application on Ubuntu https://learn.chef.io/manage-a-web-app/ubuntu .
I have been using 2 vagrant boxes. one for workstation and the second as
node. When running the bootstraping command it complains about: “Halite is
not compatible with no_lazy_load false, please set no_lazy_load true in
your Chef configuration file.” Not having much information about his, I
headed to poise project on github and found that I could set the
no_lazy_load to true. I had to manually and run chef-client but that has
resulted in another error reported here https://learn.chef.io/manage-a-web-app/ubuntu/apply-and-verify-your-web-server-configuration/#comment-2151426919
Can anyone please give a helping hand here?
–
Joseph Kodjo-Kuma Djomeda
check out my pains at : www.mycodingpains.com
We become what we think about ourselves…
I wanted to be familiar with working with chef-server so after playing with chef-solo I headed to the official tutorials. So I have successfully finished the first and second tutorial but I have been struggling for a while now on the Learn to manage a basic web application on Ubuntu .
I have been using 2 vagrant boxes. one for workstation and the second as node. When running the bootstraping command it complains about: “Halite is not compatible with no_lazy_load false, please set no_lazy_load true in your Chef configuration file.” Not having much information about his, I headed to poise project on github and found that I could set the no_lazy_load to true. I had to manually and run chef-client but that has resulted in another error reported here https://learn.chef.io/manage-a-web-app/ubuntu/apply-and-verify-your-web-server-configuration/#comment-2151426919
Can anyone please give a helping hand here?
My cookbooks are only compatible with Chef 12 and above. You are using 11.8.2, which is not supported. Please upgrade to Chef 12 and try again.
I wanted to be familiar with working with chef-server so after playing
with chef-solo I headed to the official tutorials. So I have successfully
finished the first and second tutorial but I have been struggling for a
while now on the Learn to manage a basic web application on Ubuntu .
I have been using 2 vagrant boxes. one for workstation and the second as
node. When running the bootstraping command it complains about: “Halite is
not compatible with no_lazy_load false, please set no_lazy_load true in
your Chef configuration file.” Not having much information about his, I
headed to poise project on github and found that I could set the
no_lazy_load to true. I had to manually and run chef-client but that has
resulted in another error reported here
Joseph,
I imagine that you use Knife when bootstrapping a node. I do believe that
it doesn’t matter what version of ChefDK you use, when bootstrapping a
node, the Chef Omnibus installer will fetch the latest release of
chef-client and install it on the node. I believe that’s currently 12.4.1.
You can override that by adding a --bootstrap-version flag to the knife
bootstrap command. You can also override that by hard-coding the desired
version of chef-client in your workstation’s knife.rb, or in your
Vagrantfile, or in your .kitchen.yml, if you use any of those tools.
Fabien
On Thu, Jul 23, 2015 at 8:55 AM, Joseph Djomeda joseph@djomeda.com wrote:
Hello Noah,
Thanks for the information. is it possible to get chefdk 0.6.2 to install
chef-client 12 instead when bootstraping nodes ?
I wanted to be familiar with working with chef-server so after playing
with chef-solo I headed to the official tutorials. So I have successfully
finished the first and second tutorial but I have been struggling for a
while now on the Learn to manage a basic web application on Ubuntu .
I have been using 2 vagrant boxes. one for workstation and the second
as node. When running the bootstraping command it complains about: “Halite
is not compatible with no_lazy_load false, please set no_lazy_load true in
your Chef configuration file.” Not having much information about his, I
headed to poise project on github and found that I could set the
no_lazy_load to true. I had to manually and run chef-client but that has
resulted in another error reported here
Joseph,
I imagine that you use Knife when bootstrapping a node. I do believe that
it doesn’t matter what version of ChefDK you use, when bootstrapping a
node, the Chef Omnibus installer will fetch the latest release of
chef-client and install it on the node. I believe that’s currently 12.4.1.
You can override that by adding a --bootstrap-version flag to the knife
bootstrap command. You can also override that by hard-coding the desired
version of chef-client in your workstation’s knife.rb, or in your
Vagrantfile, or in your .kitchen.yml, if you use any of those tools.
Fabien
On Thu, Jul 23, 2015 at 8:55 AM, Joseph Djomeda joseph@djomeda.com
wrote:
Hello Noah,
Thanks for the information. is it possible to get chefdk 0.6.2 to install
chef-client 12 instead when bootstraping nodes ?
I wanted to be familiar with working with chef-server so after playing
with chef-solo I headed to the official tutorials. So I have successfully
finished the first and second tutorial but I have been struggling for a
while now on the Learn to manage a basic web application on Ubuntu .
I have been using 2 vagrant boxes. one for workstation and the second
as node. When running the bootstraping command it complains about: “Halite
is not compatible with no_lazy_load false, please set no_lazy_load true in
your Chef configuration file.” Not having much information about his, I
headed to poise project on github and found that I could set the
no_lazy_load to true. I had to manually and run chef-client but that has
resulted in another error reported here
Joseph,
I imagine that you use Knife when bootstrapping a node. I do believe that
it doesn’t matter what version of ChefDK you use, when bootstrapping a
node, the Chef Omnibus installer will fetch the latest release of
chef-client and install it on the node. I believe that’s currently 12.4.1.
You can override that by adding a --bootstrap-version flag to the knife
bootstrap command. You can also override that by hard-coding the desired
version of chef-client in your workstation’s knife.rb, or in your
Vagrantfile, or in your .kitchen.yml, if you use any of those tools.
Fabien
On Thu, Jul 23, 2015 at 8:55 AM, Joseph Djomeda joseph@djomeda.com
wrote:
Hello Noah,
Thanks for the information. is it possible to get chefdk 0.6.2 to
install chef-client 12 instead when bootstraping nodes ?
I wanted to be familiar with working with chef-server so after
playing with chef-solo I headed to the official tutorials. So I have
successfully finished the first and second tutorial but I have been
struggling for a while now on the Learn to manage a basic web application
on Ubuntu .
I have been using 2 vagrant boxes. one for workstation and the second
as node. When running the bootstraping command it complains about: “Halite
is not compatible with no_lazy_load false, please set no_lazy_load true in
your Chef configuration file.” Not having much information about his, I
headed to poise project on github and found that I could set the
no_lazy_load to true. I had to manually and run chef-client but that has
resulted in another error reported here