Foreman 1.7.0-RC1 now available for testing

Support
1

I'm happy to announce that we've reached the start of the Foreman 1.7
cycle, and it's time to ask for your help in testing and
battle-hardening our new release candidates.

All help is appreciated to ensure our dot-zero release is solid, either
installing a new instance or upgrading a test server.

Headline features

··· ================= Foreman 1.7 features a handful of exciting enhancements to smart class parameters, providing better control over default values and merging of values across matchers.

A new build review page helps you check for common errors when switching
a host into build mode, such as template rendering problems.

Networking has been a big focus over the past few months, with support
for specifying bonds, VLANs and aliased interfaces on a host, importing
them from facts and using that information in provisioning templates and
via the ENC.

Two existing features have been moved into plugins, so they can be
developed outside of Foreman’s release cycle. If you’re using the
Rundeck integration, you should install the foreman_host_rundeck plugin,
and if you’re using the Chef Proxy feature then install the
smart_proxy_chef plugin to replace it.

This also marks the end of Debian 6 (Squeeze) support, and Ruby 1.8.7 in
the Foreman application (not the proxy or installer).

Much more information about the changes in Foreman 1.7 is available in
our release notes:
http://theforeman.org/manuals/1.7/index.html#Releasenotesfor1.7

Upgrading or installing

When upgrading, follow these instructions and please take note of the
known issues and warnings (especially Ubuntu 12.04 users):
http://theforeman.org/manuals/1.7/index.html#3.6Upgrade
http://theforeman.org/manuals/1.7/index.html#Deprecationwarnings

If you’re installing a new test instance, follow the quickstart:
http://theforeman.org/manuals/1.7/index.html#2.Quickstart

Packages may be found in the 1.7 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:
730A 9338 F93E E729 2EAC 2052 4C25 8BD4 2D76 2E88
(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
Red Hat Engineering

2

Thank you very much for all those nice features and additions that we'll be
happy to deploy and test!!!

Now for the bad news:

On our rig, upgrading fails when migrating the db.

== AddUniqueIndexToParameter: migrating

··· ====================================== -- add_index(:parameters, [:reference_id, :name], {:unique=>true}) rake aborted! StandardError: An error has occurred, all later migrations canceled:

Mysql2::Error: Duplicate entry ‘4-lag-members’ for key
’index_parameters_on_reference_id_and_name’: CREATE UNIQUE INDEX
index_parameters_on_reference_id_and_name ON parameters
(reference_id,
name)/usr/share/foreman/vendor/ruby/1.9.1/gems/activerecord-3.2.20/lib/active_record/connection_adapters/abstract_mysql_adapter.rb:245:in
`query’
(etc.)

This is caused because 20140805114754_add_unique_index_to_parameter.rb
tries to add the mentioned index. However, in my db, I have:

id name ref_id type
1 lag-members 4 GroupParameter
3 lag-members 4 HostParameter

Which leads to the SQL violation.

I’ve registered Bug #8366: Upgrade from 1.6.2 to 1.7rc1 fails during AddUniqueIndexToParameter db migration with duplicate key error - Foreman for this. Am I
correct in assuming reference_id is the id of the db object of type?
Shouldn’t that be added to the index in that case?

As a side note, lag-members will be deprecated in favour of the new network
interface :wink:

Kind regards,

Ronald van Zantvoort

On Tuesday, 11 November 2014 17:11:00 UTC+1, Dominic Cleal wrote:

I’m happy to announce that we’ve reached the start of the Foreman 1.7
cycle, and it’s time to ask for your help in testing and
battle-hardening our new release candidates.

All help is appreciated to ensure our dot-zero release is solid, either
installing a new instance or upgrading a test server.

Headline features

Foreman 1.7 features a handful of exciting enhancements to smart class
parameters, providing better control over default values and merging of
values across matchers.

A new build review page helps you check for common errors when switching
a host into build mode, such as template rendering problems.

Networking has been a big focus over the past few months, with support
for specifying bonds, VLANs and aliased interfaces on a host, importing
them from facts and using that information in provisioning templates and
via the ENC.

Two existing features have been moved into plugins, so they can be
developed outside of Foreman’s release cycle. If you’re using the
Rundeck integration, you should install the foreman_host_rundeck plugin,
and if you’re using the Chef Proxy feature then install the
smart_proxy_chef plugin to replace it.

This also marks the end of Debian 6 (Squeeze) support, and Ruby 1.8.7 in
the Foreman application (not the proxy or installer).

Much more information about the changes in Foreman 1.7 is available in
our release notes:
Foreman :: Manual

Upgrading or installing

When upgrading, follow these instructions and please take note of the
known issues and warnings (especially Ubuntu 12.04 users):
Foreman :: Manual
Foreman :: Manual

If you’re installing a new test instance, follow the quickstart:
Foreman :: Manual

Packages may be found in the 1.7 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:
730A 9338 F93E E729 2EAC 2052 4C25 8BD4 2D76 2E88
(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
Red Hat Engineering