Foreman 1.12.0-RC3 available for testing

Our third release candidate for the new 1.12 series is now available,
Foreman 1.12.0-RC3. It includes a security fix (CVE-2016-4475) and
regression fixed when editing Puppet classes and adding subnets.

It's likely that Foreman 1.12.0 will be released shortly. Thanks to
those who have been testing and reporting issues with the RCs so far.

Installation quick start:

Upgrade instructions:

Release notes:

Changes in this release

··· ======================= Some notable changes in this release are listed below, so we'll be particularly looking out for new issues in these areas:
  1. Puppet 4 support in the installer, including setting up Puppet Server
    when using a Puppet Agent (AIO).

  2. Puppet 4 support in the smart proxy, using a new API available in
    Puppet Server to import environments and classes instead of parsing.

  3. Ruby on Rails upgraded from version 4.1 to 4.2, under the covers.

Lots more features can be found listed in the release notes by
category, please have a look through for anything that you might rely
on and give it a test:

Do take note of the upgrade warnings and deprecations in this release:

Our list of supported OSes has changed, so please check these when
setting up new installations or upgrading.

We also have an experimental guide to upgrading a combined Foreman 1.12
and Puppet 3 installation to a Puppet 4 installation:


Packages may be found in the 1.12 directories on both
and, and tarballs are on

The GPG key used for RPMs and tarballs has the following fingerprint:
860D D70A 378A 84CE 8D47 C10E B507 F6A6 7D49 2D06
(Foreman :: Security)

Bug reporting

If you come across a bug in your testing, please file it and note the
version of Foreman that you’re using in the report.

Foreman: Foreman
Proxy: Foreman

Dominic Cleal


I successfully upgraded a test VM from 1.11 to 1.12RC3 on a puppet 3.8.5
I also upgraded the foreman-proxy on a test puppet4/puppetserver with no issue… and I even could import the puppet4 classes from that proxy into a foreman 1.11.

One thing to note though : even if that's not foreman and even if that is a VM, the CPU goes 100% on the puppetserver during the classes import and the whole process takes about 3-5 mins. on my setup, that is to say, as much as with the puppet 3.X import. But that's probably something to blame on puppet.
When that happens, there is almost no IOPS on the VM.
That's strange though because a puppet run on that puppetserver VM usually takes 18s, compared to the ~50s on most bare metal servers (with my setup/modules)…

Anyway : great work, thanks !