Installation now requires newer version of kernel for passenger

Support
1

All,

Our automation for upstream builds have shown the following error message:

[w.x.y.z] out: [ERROR 2016-05-30 20:07:57 verbose] Execution of
'/usr/bin/yum -d 0 -e 0 -y install mod_passenger' returned 1: !!!
PASSENGER CANNOT BE INSTALLED: KERNEL TOO OLD !!!
[w.x.y.z] out: [ INFO 2016-05-30 20:07:57 verbose]
[w.x.y.z] out: [ INFO 2016-05-30 20:07:57 verbose] You are currently
running kernel 2.6.32-642.el6.x86_64, with SELinux policy
[w.x.y.z] out: [ INFO 2016-05-30 20:07:57 verbose] version 24. However,
Passenger's SELinux policy requires kernel >= 2.6.39,
[w.x.y.z] out: [ INFO 2016-05-30 20:07:57 verbose] with support for
policy version >= 25.
[w.x.y.z] out: [ INFO 2016-05-30 20:07:57 verbose]
[w.x.y.z] out: [ INFO 2016-05-30 20:07:57 verbose] There are two ways to
solve this problem:
[w.x.y.z] out: [ INFO 2016-05-30 20:07:57 verbose]
[w.x.y.z] out: [ INFO 2016-05-30 20:07:57 verbose] Alternative 1:
upgrade your kernel to at least 2.6.39, then reinstall
[w.x.y.z] out: [ INFO 2016-05-30 20:07:57 verbose] Passenger.
[w.x.y.z] out: [ INFO 2016-05-30 20:07:57 verbose]
[w.x.y.z] out: [ INFO 2016-05-30 20:07:57 verbose] -OR-
[w.x.y.z] out: [ INFO 2016-05-30 20:07:57 verbose]
[w.x.y.z] out: [ INFO 2016-05-30 20:07:57 verbose] Alternative 2:
disable SELinux.
[w.x.y.z] out: [ INFO 2016-05-30 20:07:57 verbose] Edit
/etc/selinux/config, set SELINUX=disabled, reboot, then
[w.x.y.z] out: [ INFO 2016-05-30 20:07:57 verbose] reinstall Passenger.
[w.x.y.z] out: [ INFO 2016-05-30 20:07:57 verbose]
[w.x.y.z] out: [ERROR 2016-05-30 20:07:57 verbose]
%pre(passenger-5.0.28-8.el6.x86_64) scriptlet failed, exit status 1
[w.x.y.z] out: [ INFO 2016-05-30 20:07:57 verbose] Error in PREIN scriptlet
in rpm package passenger-5.0.28-8.el6.x86_64
[w.x.y.z] out: [ERROR 2016-05-30 20:07:57 verbose] install: %pre
scriptlet failed (2), skipping passenger-5.0.28-8.el6

Is this the direction we're going with upstream? Are we now requiring a
newer version of the kernel for new installations?

Thanks in advance for your clarification,

Og

2

If you're using nightlies, this is due to issue
Bug #14789: puppetlabs-apache 1.9.0 adds phusionpassenger yum repo - Installer - Foreman. Disable SELinux, use a
stable release or use EL7 in the meantime.

··· On 31/05/16 14:19, Og Maciel wrote: > All, > > Our automation for upstream builds have shown the following error message: > > [w.x.y.z] out: [ERROR 2016-05-30 20:07:57 verbose] Execution of > '/usr/bin/yum -d 0 -e 0 -y install mod_passenger' returned 1: !!!! > PASSENGER CANNOT BE INSTALLED: KERNEL TOO OLD !!!!

–
Dominic Cleal
dominic@cleal.org

3

Yes, we're using nightlies. Sadly, EL7 has its own set of failures for us:

[DEBUG 2016-05-30 20:11:10 main] Class[Foreman::Service]: The container
Stage[main] will propagate my refresh event
[DEBUG 2016-05-30 20:11:10 main] Failed to load library 'foreman_api' for
feature 'foreman_api'
[DEBUG 2016-05-30 20:11:10 main]
Puppet::Type::Foreman_smartproxy::ProviderRest: feature foreman_api is
missing
[DEBUG 2016-05-30 20:11:10 main] Failed to load library 'apipie_bindings'
for feature 'apipie_bindings'
[DEBUG 2016-05-30 20:11:10 main]
Puppet::Type::Foreman_smartproxy::ProviderRest_v2: feature apipie_bindings
is missing

Is there a known issue for this as well?

··· On Tuesday, May 31, 2016 at 9:26:13 AM UTC-4, Dominic Cleal wrote: > > If you're using nightlies, this is due to issue > http://projects.theforeman.org/issues/14789. Disable SELinux, use a > stable release or use EL7 in the meantime. >
4

>
> If you're using nightlies, this is due to issue
> Bug #14789: puppetlabs-apache 1.9.0 adds phusionpassenger yum repo - Installer - Foreman
> <Bug #14789: puppetlabs-apache 1.9.0 adds phusionpassenger yum repo - Installer - Foreman>. Disable SELinux, use a
> stable release or use EL7 in the meantime.
>
>
> Yes, we're using nightlies. Sadly, EL7 has its own set of failures for us:

Actually EL7 is affected by the same issue in a different way, you will
need to disable SELinux.

> [DEBUG 2016-05-30 20:11:10 main] Class[Foreman::Service]: The container
> Stage[main] will propagate my refresh event
> [DEBUG 2016-05-30 20:11:10 main] Failed to load library 'foreman_api'
> for feature 'foreman_api'
> [DEBUG 2016-05-30 20:11:10 main]
> Puppet::Type::Foreman_smartproxy::ProviderRest: feature foreman_api is
> missing
> [DEBUG 2016-05-30 20:11:10 main] Failed to load library
> 'apipie_bindings' for feature 'apipie_bindings'
> [DEBUG 2016-05-30 20:11:10 main]
> Puppet::Type::Foreman_smartproxy::ProviderRest_v2: feature
> apipie_bindings is missing
>
> Is there a known issue for this as well?

Those are DEBUG messages, not failures. Whatever your failure is, it
probably isn't that.

··· On 31/05/16 14:56, Og Maciel wrote: > On Tuesday, May 31, 2016 at 9:26:13 AM UTC-4, Dominic Cleal wrote:

–
Dominic Cleal
dominic@cleal.org