ShellOut | Easily run shell commands from a Swift script | Command Line Interface library

You don't need the echo command to get the output. you can directly run the command through mixlib/shellout and get then get the command output from stdout.

Going by the results of search for this issue, it could be temporary. However for the time being you could change disable the GPG check for the repository in /etc/yum.repos.d/pgdg-redhat-all.repo.

The error indicates GPG verification issue for [pgdg-common] repo, but this could be for other repos in the pgdg-redhat-all.repo file. This is usually enabled with gpgcheck=1.

Changing this to gpgcheck=0 for all occurrences using something like Chef::Util::FileEdit should work in the meantime.

I did a bit more research, and based on some hints, I added an additional line:

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 are creating 4 nearly identical resources all named execute[Create_scripts] and when the notification fires from the first cookbook_file resource being updated it finds the last one of them to be notified and runs against test4 (no matter which cookbook_file resource updates).

The fix is to use string interpolation to change the name of the execute resources to be unique and to notify based on that unique name:

Turns out, you can use the system() function for C++ in Swift!

First, I created a new target in my package (to get past language mixing errors):