chef-client | Development repository for Chef Client cookbook | Infrastructure Automation library

A workaround could be to set the email_hash as an attribute, report handler can access the node object with the node method o you could do run_status.node['email_hash'][xxx] instead of email_hash[xxx].

Doc around the run_status object in handlers is here

For a more detailed exchange, feel free to join Chef's slack for community help (and there's Chef's devs there too which help a lot for inner bits): https://community-slack.chef.io/

The issue is occurring because a new property was added in Chef 14.2 to the execute resource.

default_env

Ruby Type: true, false | Default Value: false

When true this enables ENV magic to add path_sanity to the PATH and force the locale to English+UTF-8 for parsing output

New in Chef Client 14.2

This is why /sbin/pvcreate was run (though it failed), but not pvdisplay.

There is further explanation for this on client.rb configuration.

enforce_path_sanity

Turn on path sanity in resources that shellout so that expected paths like /sbin or /bin are added to the PATH. Disabled by default.

You could fix it in different ways:

1. Use absolute path for commands in your execute/bash resource. Example:

You shouldn't be using resources with the same name, that actually do different things. You have 3 resources in the resource collection eventually with the same name: execute 'Run tune2fs', but every one of them doing its own thing, because the command "tune2fs -i 0 -c 0 /dev/#{val_hash['vg_name']}/#{lv_name}" are different.

Chef just does not know which resource of 3, you are notifying with

notifies :run, "execute[Run tune2fs]", :immediately

Use different names for your execute resources:

Due space issue i was facing this. Now i resolved it

Not sure what's the correlation between the version and this behavior. But seems the fstype cur_type in mount resource is getting nil value. You might want to check on why cur_type is not getting set to the value you expect.

Couple of clues that indicate that the issue is with how the cur_type variable is set:

1. Note that in the mount command: "mount", "-t", "-o", there should be a filesytem type before -o (options).

2. In the Compiled Resource:, we can see fstype nil where you are passing the cur_type variable.

Please check how the cur_type variable is being set. Seems there is a change that is causing to not be set in new version of Chef. You could update your question with that details too.

You need to use the v5.0.0 version of that cookbook which has support for Chef Infra Client 16:

https://github.com/aespinosa/cookbook-kube/commit/f95626f6ce00b9f8c9cf94fbcb87dfffb74d00c2

This looks like a chef-client issue. I think you are using chef 14+.

That raises a few questions :

• What is the chef-client version used in your projects ?
• if its Chef 14+ , try using the latest supermarket cookbook
• Else, follow the instructions below.

In your kitchen.yml, try downgrading the chef-client under the provisioner section. Refer the below snippet :

I think step 3 is wrong in documentation. It should be like this:

you can test whether docker engine is installed in many ways, here are some.

• check whether docker command exist