Upgrade Chef Infra Server

Chef Infra Server Upgrade Matrix

Running Version	Upgrade Version	License	Version Support
13	14	Yes	Yes
12.17.15	14	Yes	Yes
12.3.0	12.17.15	No	No
11	12.3.0	No	No

License: Chef Infra Server 13 and 14 are governed by the Chef License. You will be required to accept these terms when using Chef Infra Server 13 or 14 for the first time by entering Yes when prompted.
Version Support: Chef Infra Server 13 and 14 are supported Chef Software distributions. Earlier versions are no longer supported. For more information about supported Chef Software see the Supported Versions documentation.

Upgrading to Chef Infra Server

Three upgrade scenarios exist for upgrades from Chef Infra Server 12.17.15 to Chef Infra Server 13 or 14:

Standalone
Chef Backend (HA)
Tiered

Chef Infra Server 14

Warning

Do not upgrade your production server. First, upgrade in your test server, and then upgrade your production server.

Chef Infra Server 14 uses Elasticsearch as its search index. The Chef Infra Server 14 upgrade process requires downtime for stopping the server, installing the new package, and then upgrading the server, which will include an automatic Elasticsearch reindexing operation for existing Solr users. We estimate the reindexing operation will take 2 minutes for each 1000 nodes, but the it could take more time, depending on your server hardware and the complexity of your Chef data.

The Chef Infra Server 14 upgrade does not reindex existing external Elasticsearch installations.

Chef Infra Server 12.17.15 or Later

Warning

Upgrade Chef Infra Server and any add-ons to compatible versions before setting insecure_addon_compat to false.

As of version 12.14, Chef Infra Server renders passwords inside of the /etc/opscode directory by default. If you are using Chef Infra Server without add-ons, or if you are using the latest add-ons versions, you can set insecure_addon_compat to false in `/etc/opscode/chef-server.rb. and Chef Infra Server will write all credentials to a single location.

For more information on password generation, including a list of supported add-on versions, see Chef Infra Server Credentials Management.

Standalone Upgrade

The Chef Infra Server 14 upgrade process requires downtime for stopping the server, installing the new package, and then upgrading the server, which will include an automatic Elasticsearch reindexing operation for existing Solr users. We estimate the reindexing operation will take 2 minutes for each 1000 nodes, but the it could take more time, depending on your server hardware and the complexity of your Chef data.

Standalone Upgrade Steps

Back up your Chef Infra Server data before starting the upgrade process using knife-ec-backup.
Confirm that the Chef Infra Server services are operational:
```
chef-server-ctl reconfigure
```
Download the desired Chef Infra Server version from the Chef Infra Server Downloads page.
Stop the server:
```
chef-server-ctl stop
```

Install the Chef Infra Server package:

To install with dpkg:

dpkg -i /path/to/chef-server-core-<version>.deb

To install with the RPM Package Manager:

rpm -Uvh --nopostun /path/to/chef-server-core-<version>.rpm

Upgrade the server and accept the Chef Software license by entering Yes at the prompt:
```
chef-server-ctl upgrade
```
To accept the license and upgrade in one command:
```
CHEF_LICENSE='accept' chef-server-ctl upgrade
```
Start Chef Infra Server:
```
chef-server-ctl start
```
Upgrade any Chef Infra Server add-ons.
After the upgrade process is complete, test and verify that the server works properly.
Clean up the server by removing the old data:
```
chef-server-ctl cleanup
```

Chef Backend Upgrade

The Chef Infra Server can operate in a high availability configuration that provides automated load balancing and failover for stateful components in the system architecture.

To upgrade your Chef Backend installation, see High Availability: Upgrade to Chef Backend 2.

Tiered Upgrade

This section describes the upgrade process from a tiered server configuration.

The Chef Infra Server 14 upgrade process requires downtime for stopping the server, installing the new package, and then upgrading the server, which will include an automatic Elasticsearch reindexing operation for existing Solr users. We estimate the reindexing operation will take 2 minutes for each 1000 nodes, but the it could take more time, depending on your server hardware and the complexity of your Chef data.

Note

These instructions are intended for users of the Chef Infra Server tier topology. For the latest information on setting up a highly-available server cluster, see High Availability: Backend Cluster.

Tiered Upgrade Steps

To upgrade to Chef Infra Server on a tiered Chef Infra Server configuration, do the following:

Back up the Chef Infra Server data before starting the upgrade process using knife-ec-backup.
Confirm that the Chef Infra Server services are operational:
```
chef-server-ctl reconfigure
```
Download the desired Chef Infra Server version from the Chef Infra Server Downloads page, then copy it to each server.
Stop all front end servers:
```
chef-server-ctl stop
```
Install the Chef Infra Server package on all servers:
To install with dpkg:
```
dpkg -i /path/to/chef-server-core-<version>.deb
```
To install with the RPM Package Manager:
```
rpm -Uvh --nopostun /path/to/chef-server-core-<version>.rpm
```
Stop the back end server:
```
chef-server-ctl stop
```
Upgrade the server and accept the Chef Software license by entering Yes at the prompt:
```
chef-server-ctl upgrade
```
To accept the license and upgrade in one command:
```
CHEF_LICENSE='accept' chef-server-ctl upgrade
```
Copy the entire /etc/opscode directory from the back end server to all front end servers:
```
scp -r /etc/opscode <each server's IP>:/etc
```
Upgrade each of the front end servers:
```
chef-server-ctl upgrade
```
Run the following command on both the front end, and back end servers:
```
chef-server-ctl start
```
Upgrade any Chef Infra Server add-ons.
After the upgrade process is complete, test and verify that the server works properly.
Clean up the server by removing the old data:
```
chef-server-ctl cleanup
```

Upgrading Add-ons

Chef Infra Server 13 and 14 support Chef Manage. This add-on is deprecated. Chef Manage will reach EOL on December 31, 2021. After upgrading Chef Infra Server, reinstall the add-on and then reconfigure Chef Infra Server and the add-on.

Chef Manage: Chef Manage is deprecated and will reach EOL on December 31, 2021. Chef Manage is a management console for data bags, attributes, run-lists, roles, environments, and cookbooks from a web user interface

Use Downloads

The install subcommand downloads packages from https://downloads.chef.io by default. For systems that are not behind a firewall (and have connectivity to https://downloads.chef.io), these packages can be installed as described below.

Install add-ons

Install Chef Manage with:

sudo chef-server-ctl install chef-manage

Reconfigure the server
```
sudo chef-server-ctl reconfigure
```
Reconfigure add-ons
Reconfigure Chef Manage with:
```
sudo chef-manage-ctl reconfigure
```

Finally, accept the Chef License:

sudo chef-manage-ctl reconfigure --accept-license

Use Local Packages

Use the install subcommand with the --path option to install the Chef Manage (chef-manage) add-on for Chef Infra Server.

sudo chef-server-ctl install PACKAGE_NAME --path /path/to/package/directory

For example:

sudo chef-server-ctl install chef-manage --path /root/packages

The chef-server-ctl command will install the first chef-manage package found in the /root/packages directory.

Was this page helpful?