Foreman 1.12.0-RC1 available for testing

Today we make the first release candidate for Foreman 1.12.0 available
for testing - please help by trying it out, reporting and fixing bugs.

This first release candidate includes new versions of Foreman, Smart
Proxy and Foreman Installer. The next release candidate should also
include a new version of Hammer CLI.

Installation quick start:
https://theforeman.org/manuals/1.12/quickstart_guide.html

Upgrade instructions:
https://theforeman.org/manuals/1.12/index.html#3.6Upgrade

Release notes:
https://theforeman.org/manuals/1.12/index.html#Releasenotesfor1.12

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:
https://theforeman.org/manuals/1.12/index.html#Releasenotesfor1.12

Do take note of the upgrade warnings and deprecations in this release:
https://theforeman.org/manuals/1.12/index.html#Upgradewarnings

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:
http://projects.theforeman.org/projects/foreman/wiki/Upgrading_from_Puppet_3_to_4

Downloads

Packages may be found in the 1.12 directories on both deb.foreman.org
and yum.theforeman.org, and tarballs are on downloads.theforeman.org.

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
Installer:
Foreman


Dominic Cleal
dominic@cleal.org

Hi there

I'm trying to upgrade from version 1.11.1 to 1.12 RC1 on RHEL7 but yum
upgrade fails with a dependency problem.

–> Finished Dependency Resolution
Error: Package: tfm-rubygem-protected_attributes-1.1.3-3.el7.noarch
(sync-rhel7-foreman-112)
Requires: sclo-ror42-rubygem(activemodel) >= 4.0.1
Error: Package:
tfm-rubygem-validates_lengths_from_database-0.5.0-3.el7.noarch
(sync-rhel7-foreman-112)
Requires: sclo-ror42-rubygem(activerecord) >= 2.3.2
Error: Package: tfm-rubygem-activerecord-session_store-0.1.2-2.el7.noarch
(sync-rhel7-foreman-112)
Requires: sclo-ror42-rubygem(actionpack) >= 4.0.0
Error: Package: tfm-rubygem-rack-jsonp-1.3.1-5.el7.noarch
(sync-rhel7-foreman-112)
Requires: sclo-ror42-rubygem(rack)
Error: Package: tfm-rubygem-activerecord-session_store-0.1.2-2.el7.noarch
(sync-rhel7-foreman-112)
Requires: sclo-ror42-rubygem(railties) >= 4.0.0
[… snip …]

An up to date Softwarecollections channel from redhat is avialable.
These packages are available but called "rh-ror42-rubygem-xxx" and not
"sclo-ror42-rubygem-xxx"

Is the redhat variant of the SCL repo no longer supported? Do we need to
switch to the upstream one?

Thanks
Sandro

··· On Monday, June 6, 2016 at 1:43:51 PM UTC+2, Dominic Cleal wrote: > > Today we make the first release candidate for Foreman 1.12.0 available > for testing - please help by trying it out, reporting and fixing bugs. > > This first release candidate includes new versions of Foreman, Smart > Proxy and Foreman Installer. The next release candidate should also > include a new version of Hammer CLI. > > Installation quick start: > https://theforeman.org/manuals/1.12/quickstart_guide.html > > Upgrade instructions: > https://theforeman.org/manuals/1.12/index.html#3.6Upgrade > > Release notes: > https://theforeman.org/manuals/1.12/index.html#Releasenotesfor1.12 > > > 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: > https://theforeman.org/manuals/1.12/index.html#Releasenotesfor1.12 > > Do take note of the upgrade warnings and deprecations in this release: > https://theforeman.org/manuals/1.12/index.html#Upgradewarnings > > 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: > > http://projects.theforeman.org/projects/foreman/wiki/Upgrading_from_Puppet_3_to_4 > > > Downloads > ========= > Packages may be found in the 1.12 directories on both deb.foreman.org > and yum.theforeman.org, and tarballs are on downloads.theforeman.org. > > The GPG key used for RPMs and tarballs has the following fingerprint: > 860D D70A 378A 84CE 8D47 C10E B507 F6A6 7D49 2D06 > (https://theforeman.org/security.html#GPGkeys) > > > 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: http://projects.theforeman.org/projects/foreman/issues/new > Proxy: http://projects.theforeman.org/projects/smart-proxy/issues/new > Installer: > http://projects.theforeman.org/projects/puppet-foreman/issues/new > > -- > Dominic Cleal > dom...@cleal.org > >

> Hi there
>
> I'm trying to upgrade from version 1.11.1 to 1.12 RC1 on RHEL7 but yum
> upgrade fails with a dependency problem.
>
> --> Finished Dependency Resolution
> Error: Package: tfm-rubygem-protected_attributes-1.1.3-3.el7.noarch
> (sync-rhel7-foreman-112)
> Requires: sclo-ror42-rubygem(activemodel) >= 4.0.1
> [… snip …]
>
> An up to date Softwarecollections channel from redhat is avialable.
> These packages are available but called "rh-ror42-rubygem-xxx" and not
> "sclo-ror42-rubygem-xxx"

We use the sclo-ror42 collection from CentOS and not rh-ror42.

> Is the redhat variant of the SCL repo no longer supported? Do we need to
> switch to the upstream one?

Correct, please see the upgrade instructions and RPM information:

https://theforeman.org/manuals/1.12/index.html#3.6Upgrade
https://theforeman.org/manuals/1.12/index.html#3.3.1RPMPackages

··· On 07/06/16 10:30, Sandro Roth wrote:


Dominic Cleal
dominic@cleal.org

Ah sorry, classic case of RTFM :slight_smile:

Thanks

··· On Tuesday, June 7, 2016 at 11:32:52 AM UTC+2, Dominic Cleal wrote: > > On 07/06/16 10:30, Sandro Roth wrote: > > Hi there > > > > I'm trying to upgrade from version 1.11.1 to 1.12 RC1 on RHEL7 but yum > > upgrade fails with a dependency problem. > > > > --> Finished Dependency Resolution > > Error: Package: tfm-rubygem-protected_attributes-1.1.3-3.el7.noarch > > (sync-rhel7-foreman-112) > > Requires: sclo-ror42-rubygem(activemodel) >= 4.0.1 > > [... snip ...] > > > > An up to date Softwarecollections channel from redhat is avialable. > > These packages are available but called "rh-ror42-rubygem-xxx" and not > > "sclo-ror42-rubygem-xxx" > > We use the sclo-ror42 collection from CentOS and not rh-ror42. > > > Is the redhat variant of the SCL repo no longer supported? Do we need to > > switch to the upstream one? > > Correct, please see the upgrade instructions and RPM information: > > https://theforeman.org/manuals/1.12/index.html#3.6Upgrade > https://theforeman.org/manuals/1.12/index.html#3.3.1RPMPackages > > -- > Dominic Cleal > dom...@cleal.org >