Foreman 1.10.1 bug fix release

Support
1

Foreman 1.10.1 is now available, with over seventy bug fixes across
the application and a new version of the Hammer CLI.

Full release notes for all of the changes are on the website here:
http://theforeman.org/manuals/1.10/index.html#Releasenotesfor1.10.1
http://projects.theforeman.org/rb/release/104

If you've been hesitating on an upgrade to Foreman 1.10, then now is
the time to do it with the improvements available in this point release.

Thanks for the detailed bug reports and help fixing issues over the
past few weeks, and welcome to our new contributors.

==== Upgrading ====
When upgrading, follow these instructions:
http://theforeman.org/manuals/1.10/index.html#3.6Upgrade

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

Packages may be found in the 1.10 directories on both deb.foreman.org
and yum.theforeman.org, and tarballs are on downloads.theforeman.org.
Foreman 1.10 adds Debian packages for armhf (v7).

The GPG key used for RPMs and tarballs has the following fingerprint:
9EFD 673A 649D 77F5 C615 44AC C1B2 621D BE67 E9DA
(Foreman :: Security)

Bug reporting

··· ============= If you come across a bug, 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

2

I need this release to fix my Katello 2.4 installation because I am
suffering from this bug here : Bug #12555: Only first FreeIPA XMLRPC call succeeds Foreman proxy 1.10 and FreeIPA, version: 4.1.4 - Smart Proxy - Foreman

Do I need to wait for another Katello release or will my katello-installer
upgrade the foreman minor release ?

··· On Wednesday, January 20, 2016 at 6:58:18 AM UTC-8, Dominic Cleal wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Foreman 1.10.1 is now available, with over seventy bug fixes across > the application and a new version of the Hammer CLI. > > Full release notes for all of the changes are on the website here: > http://theforeman.org/manuals/1.10/index.html#Releasenotesfor1.10.1 > http://projects.theforeman.org/rb/release/104 > > If you've been hesitating on an upgrade to Foreman 1.10, then now is > the time to do it with the improvements available in this point release. > > Thanks for the detailed bug reports and help fixing issues over the > past few weeks, and welcome to our new contributors. > > ==== Upgrading ==== > When upgrading, follow these instructions: > http://theforeman.org/manuals/1.10/index.html#3.6Upgrade > > If you're installing a new instance, follow the quickstart: > http://theforeman.org/manuals/1.10/index.html#2.Quickstart > > Packages may be found in the 1.10 directories on both deb.foreman.org > and yum.theforeman.org, and tarballs are on downloads.theforeman.org. > Foreman 1.10 adds Debian packages for armhf (v7). > > The GPG key used for RPMs and tarballs has the following fingerprint: > 9EFD 673A 649D 77F5 C615 44AC C1B2 621D BE67 E9DA > (http://theforeman.org/security.html#GPGkeys) > > Bug reporting > ============= > If you come across a bug, 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 > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2 > > iEYEARECAAYFAlafoH4ACgkQfH0ybywrcszN0ACfU6MnjlkxSzLEIOw6zwnqiOBh > jEsAn0z+cJRp/8t7H2jq2feTbKlZGTfc > =u2sK > -----END PGP SIGNATURE----- >
3

I'd have thought you can just upgrade the packages as our minor/patch
releases should always be compatible.

··· On 21/01/16 05:19, Nathan Peters wrote: > I need this release to fix my Katello 2.4 installation because I am > suffering from this bug here : http://projects.theforeman.org/issues/12555 > > Do I need to wait for another Katello release or will my > katello-installer upgrade the foreman minor release ?

–
Dominic Cleal
dominic@cleal.org

4

Thanks for the info. I can confirm that I simply ran a yum update and got
the newest foreman packages, and bug fix seems to have worked. My realm
proxy starting working immediately after reboot :slight_smile:

··· On Wednesday, January 20, 2016 at 11:58:59 PM UTC-8, Dominic Cleal wrote: > > On 21/01/16 05:19, Nathan Peters wrote: > > I need this release to fix my Katello 2.4 installation because I am > > suffering from this bug here : > http://projects.theforeman.org/issues/12555 > > > > Do I need to wait for another Katello release or will my > > katello-installer upgrade the foreman minor release ? > > I'd have thought you can just upgrade the packages as our minor/patch > releases should always be compatible. > > -- > Dominic Cleal > dom...@cleal.org >
5

Hmm, not able to start foreman-proxy after upgrade:

[root@spc02 ~]# /usr/share/foreman-proxy/bin/smart-proxy
/usr/share/gems/gems/smart_proxy_remote_execution_ssh-0.0.11/lib/smart_proxy_remote_execution_ssh/plugin.rb:1:in
<top (required)>': uninitialized constant Proxy::RemoteExecution (NameError) from /usr/share/rubygems/rubygems/core_ext/kernel_require.rb:55:inrequire'
from /usr/share/rubygems/rubygems/core_ext/kernel_require.rb:55:in
require&#39; from /usr/share/gems/gems/smart_proxy_remote_execution_ssh-0.0.11/lib/smart_proxy_remote_execution_ssh.rb:1:in<top (required)>'
from /usr/share/rubygems/rubygems/core_ext/kernel_require.rb:135:in
require&#39; from /usr/share/rubygems/rubygems/core_ext/kernel_require.rb:135:inrescue in require'
from /usr/share/rubygems/rubygems/core_ext/kernel_require.rb:144:in
require&#39; from /usr/share/gems/gems/bundler_ext-0.3.0/lib/bundler_ext/bundler_ext.rb:39:inblock in system_require'
from
/usr/share/gems/gems/bundler_ext-0.3.0/lib/bundler_ext/bundler_ext.rb:35:in
each&#39; from /usr/share/gems/gems/bundler_ext-0.3.0/lib/bundler_ext/bundler_ext.rb:35:insystem_require'
from /usr/share/foreman-proxy/lib/bundler_helper.rb:22:in
require_groups&#39; from /usr/share/foreman-proxy/lib/smart_proxy.rb:31:in<top
(required)>'
from /usr/share/rubygems/rubygems/core_ext/kernel_require.rb:55:in
require&#39; from /usr/share/rubygems/rubygems/core_ext/kernel_require.rb:55:inrequire'
from /usr/share/foreman-proxy/bin/smart-proxy:5:in `<main>'

[root@spc02 ~]# rpm -qa | grep remote
rubygem-smart_proxy_remote_execution_ssh-0.0.11-1.el7.noarch
tfm-rubygem-foreman_remote_execution-0.1.2-1.fm1_10.el7.noarch
[root@spc02 ~]#

Anybody else seen this?

6

Just to clarify things a bit - above example was a fresh install of 1.10.1
on CentOS 7.2.

The in-place upgrade of 1.10.0 to 1.10.1 on CentOS 7.1 results in the same
error though:

[root@spc01 ~]# systemctl -l status foreman-proxy.service
● foreman-proxy.service - Foreman Proxy
Loaded: loaded (/usr/lib/systemd/system/foreman-proxy.service; enabled;
vendor preset: disabled)
Active: failed (Result: exit-code) since Thu 2016-01-21 18:41:44 MST;
15s ago
Process: 4630 ExecStart=/usr/share/foreman-proxy/bin/smart-proxy
(code=exited, status=1/FAILURE)
Main PID: 2849 (code=killed, signal=TERM)

Jan 21 18:41:44 spc01.domain.com smart-proxy[4630]: from
/usr/share/gems/gems/bundler_ext-0.3.0/lib/bundler_ext/bundler_ext.rb:35:in
system_require&#39; Jan 21 18:41:44 spc01.domain.com smart-proxy[4630]: from /usr/share/foreman-proxy/lib/bundler_helper.rb:22:inrequire_groups'
Jan 21 18:41:44 spc01.domain.com smart-proxy[4630]: from
/usr/share/foreman-proxy/lib/smart_proxy.rb:31:in &lt;top (required)&gt;&#39; Jan 21 18:41:44 spc01.domain.com smart-proxy[4630]: from /usr/share/rubygems/rubygems/core_ext/kernel_require.rb:55:inrequire'
Jan 21 18:41:44 spc01.domain.com smart-proxy[4630]: from
/usr/share/rubygems/rubygems/core_ext/kernel_require.rb:55:in require&#39; Jan 21 18:41:44 spc01.domain.com smart-proxy[4630]: from /usr/share/foreman-proxy/bin/smart-proxy:5:in<main>'
Jan 21 18:41:44 spc01.domain.com systemd[1]: foreman-proxy.service: control
process exited, code=exited status=1
Jan 21 18:41:44 spc01.domain.com systemd[1]: Failed to start Foreman Proxy.
Jan 21 18:41:44 spc01.domain.com systemd[1]: Unit foreman-proxy.service
entered failed state.
Jan 21 18:41:44 spc01.domain.com systemd[1]: foreman-proxy.service failed.
[root@spc01 ~]#

7

> Hmm, not able to start foreman-proxy after upgrade:
>
> [root@spc02 ~]# /usr/share/foreman-proxy/bin/smart-proxy
> /usr/share/gems/gems/smart_proxy_remote_execution_ssh-0.0.11/lib/smart_proxy_remote_execution_ssh/plugin.rb:1:in
> `<top (required)>': uninitialized constant Proxy::RemoteExecution
> (NameError)
<snip>
> [root@spc02 ~]# rpm -qa | grep remote
> rubygem-smart_proxy_remote_execution_ssh-0.0.11-1.el7.noarch
> tfm-rubygem-foreman_remote_execution-0.1.2-1.fm1_10.el7.noarch
> [root@spc02 ~]#
>
> Anybody else seen this?

Looks like Bug #13274: unable to start smart proxy with ssh plugin - Foreman Remote Execution - Foreman, from a remote
execution plugin update - it appears to be in their next 0.0.12 update.

··· On 22/01/16 00:31, 'Konstantin Orekhov' via Foreman users wrote:

–
Dominic Cleal
dominic@cleal.org

8

> Looks like Bug #13274: unable to start smart proxy with ssh plugin - Foreman Remote Execution - Foreman, from a remote
> execution plugin update - it appears to be in their next 0.0.12 update.
>

Thanks! I see that it was indeed fixed (ad locally applied patch works for
me too), but do you know when the new 0.0.12 package is expected to be
released?

9

Probably today, there's a pull request up for it.

··· On 22/01/16 20:34, 'Konstantin Orekhov' via Foreman users wrote: > > Looks like http://projects.theforeman.org/issues/13274 > , from a remote > execution plugin update - it appears to be in their next 0.0.12 update. > > > Thanks! I see that it was indeed fixed (ad locally applied patch works > for me too), but do you know when the new 0.0.12 package is expected to > be released?

–
Dominic Cleal
dominic@cleal.org