# Chef Client 13.2 Released

**URL:** <https://discourse.chef.io/t/chef-client-13-2-released/11127>\
**Category:** Chef Release Announcements\
**Created:** [July 5, 2017, 9:17am UTC](https://discourse.chef.io/t/chef-client-13-2-released/11127 "2017-07-05T09:17:49Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![thommay](https://avatars.discourse-cdn.com/v4/letter/t/f08c70/32.png) [@thommay](https://discourse.chef.io/u/thommay)\
**Post date:** [July 5, 2017, 9:17am UTC](https://discourse.chef.io/t/chef-client-13-2-released/11127/1 "2017-07-05T09:17:49Z")

</div>

Ohai Chefs!

We’re happy to announce the release of Chef v13.2!

# Release Highlights

## Properly send policyfile data

When sending events back to the Chef Server, we now correctly expand the run\_list for nodes that use Policyfiles. This allows Automate to correctly report the node.

## Reconfigure between runs when daemonized

When Chef performs a reconfigure, it re-reads the configuration files. It also re-opens its log files, which facilitates log file rotation.

Chef normally will reconfigure when sent a HUP signal. As of this release if you send a HUP signal while it is converging, the reconfigure  
happens at the end of the run. This is avoids potential Ruby issues when the configuration file contains additional Ruby code that is executed.  
While the daemon is sleeping between runs, sending a SIGHUP will still cause an immediate reconfigure.

Additionally, Chef now always performs a reconfigure after every run when daemonized.

## New Deprecations

### Explicit property methods

[https://docs.chef.io/deprecations\_namespace\_collisions.html](https://docs.chef.io/deprecations_namespace_collisions.html)

In Chef 14, custom resources will no longer assume property methods are being called on `new_resource`, and instead require the resource author to be explicit.

# Ohai Release Notes 13.2:

Ohai 13.2 has been a fantastic release in terms of community involvement with new plugins, platform support, and critical bug fixes coming from community members. A huge thank you to msgarbossa, albertomurillo, jaymzh, and davide125 for their work.

## New Features

### Systemd Paths Plugin

A new plugin has been added to expose system and user paths from systemd-path (see [https://www.freedesktop.org/software/systemd/man/systemd-path.html](https://www.freedesktop.org/software/systemd/man/systemd-path.html) for details).

### Linux Network, Filesystem, and Mdadm Plugin Resilience

The Network, Filesystem, and Mdadm plugins have been improved to greatly reduce failures to collect data. The Network plugin now better finds the binaries it requires for shelling out, filesystem plugin utilizes data from multiple sources, and mdadm handles arrays in bad states.

### Zpool Plugin Platform Expansion

The Zpool plugin has been updated to support BSD and Linux in addition to Solaris.

### RPM version parsing on AIX

The packages plugin now correctly parses RPM package name / version information on AIX systems.

### Additional Platform Support

Ohai now properly detects the [Clear](https://clearlinux.org/) and [ClearOS](https://www.clearos.com/) Linux distributions.

#### Clear Linux

- platform: clearlinux
- platform\_family: clearlinux

#### ClearOS

- platform: clearos
- platform\_family: rhel

## New Deprecations

### Removal of IpScopes plugin. (OHAI-13)

[https://docs.chef.io/deprecations\_ohai\_ipscopes.html](https://docs.chef.io/deprecations_ohai_ipscopes.html)

In Chef/Ohai 14 (April 2018) we will remove the IpScopes plugin. The data returned by this plugin is nearly identical to information already returned by individual network plugins and this plugin required the installation of an additional gem into the Chef installation. We believe that few users were installing the gem and users would be better served by the data returned from the network plugins.

Please see the [CHANGELOG](https://github.com/chef/chef/blob/master/CHANGELOG.md) for the complete list of changes.

# Get the Build

As always, you can download binaries directly from [downloads.chef.io](https://downloads.chef.io/chef/13.2.20) or by using the new `mixlib-install` command line utility available in ChefDK 0.19.6 or greater.

```auto
$ mixlib-install download chef -v 13.2.20

```

Alternatively, you can install Chef using one of the following command options:

```auto
# In Shell
$ curl https://omnitruck.chef.io/install.sh | sudo bash -s -- -P chef -v 13.2.20

# In Windows Powershell
. { iwr -useb https://omnitruck.chef.io/install.ps1 } | iex; install -project chef -version 13.2.20

```

---

<div class="post-metadata">

**Author:** ![MattRay](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.chef.io/mattray/32/47_2.png) [@MattRay](https://discourse.chef.io/u/MattRay)\
**Post date:** [July 12, 2017, 10:09am UTC](https://discourse.chef.io/t/chef-client-13-2-released/11127/2 "2017-07-12T10:09:35Z")

</div>

An updated 13.2.20 ARM build is available here:

> **[chef\_13.2.20+20170712062554-1\_armhf.deb](https://www.dropbox.com/s/1tboyiic8fmf2di/chef_13.2.20%2B20170712062554-1_armhf.deb?dl=0)**
>
> Shared with Dropbox

  
Details on the build here:  

> **[Chef 13 on the BeagleBone Black UPDATED X3](https://leastresistance.wordpress.com/2017/05/12/chef-13-on-the-beaglebone-black/)**
>
> Now that the Chef client 13 is available, I decided to upgrade my ARM build to the latest release. ARM is still not officially supported, but building was fairly straightforward. I had Chef 12.17.1…

Thanks,  
Matt Ray  
Manager, Solutions Architect - APJ :: Chef  
[matt@chef.io](mailto:matt@chef.io)  
AUS: +61 457 231 372  
US: +1 512 731 2218  
mattray :: GitHub :: IRC :: Slack :: Twitter