Foreman » Packaging

It appears that is an EPEL passenger and mod_passenger upgrade that is trumping the version in the foreman's 1.11 repo.
Disabling EPEL during installation solves the install problem.

To get a successful clean install, add to the [epel] section in /etc/yum.repos.d/epel.repo, "exclude=passenger* mod_passenger"

Do not disable EPEL.

The new passenger and mod_passenger are taking precident over the correct ones in theforeman repo.

Also, does the web UI work? If not, any error displayed? If it does work, what's the error from the installer you're getting?

Please also try with SELinux set to permission (setenforce 0).

Dominic Cleal wrote:

Could you provide the output from rpm -qa \*passenger\* please? I've been testing the updates in EPEL and haven't managed to hit this problem yet - I'm not quite sure either why the Ruby 2.0.0 native support would be loaded under 2.2.0.

The problem is these two packages got pushed up to EPEL7 over the weekend:

https://dl.fedoraproject.org/pub/epel/7/x86_64/m/mod_passenger-4.0.53-4.el7.x86_64.rpm
https://dl.fedoraproject.org/pub/epel/7/x86_64/p/passenger-4.0.53-4.el7.x86_64.rpm

EPEL7 is required to install Foreman. The two packages trump the passenger packages that are in the Foreman 1.11.1 repo.

I do not believe the Jenkins clean build of Foreman happens every day (unlike the nighly Foreman builds). My understanding is, due to Rackspace cost, the clean builds in Jenkins ( http://ci.theforeman.org/ ) do not happen daily. If possible, please fire up a EL7 clean install/build of 1.11.1 and it should fail due to the passenger/mod_passenger newer versions from EPEL7

Yes, I'm quite aware, thanks. We've run multiple tests today successfully.

Could you please check my questions above, particularly the one about SELinux?

Dominic Cleal wrote:

Also, does the web UI work? If not, any error displayed? If it does work, what's the error from the installer you're getting?

Please also try with SELinux set to permission (setenforce 0).

No, the web UI does not work.

Dominic Cleal wrote:

Could you provide the output from rpm -qa \*passenger\* please? I've been testing the updates in EPEL and haven't managed to hit this problem yet - I'm not quite sure either why the Ruby 2.0.0 native support would be loaded under 2.2.0.

These are the packages when it DOESN'T work.

1. rpm -qa | grep passenger
   mod_passenger-4.0.53-4.el7.x86_64
   tfm-rubygem-passenger-4.0.18-9.10.el7.x86_64
   passenger-4.0.53-4.el7.x86_64
   tfm-rubygem-passenger-native-libs-4.0.18-9.10.el7.x86_64
   tfm-rubygem-passenger-native-4.0.18-9.10.el7.x86_64

To make it work:
yum remove passenger-4.0.53-4.el7.x86_64 mod_passenger-4.0.53-4.el7.x86_64

Then in /etc/yum.repos.d/epel.repo in the [epel] section add
exclude=passenger* mod_passenger*

Then reinstall passenger and mod_passenger (which then pulls from theforeman repo)
yum install passenger mod_passenger

Scott Worthington wrote:

Dominic Cleal wrote:

Also, does the web UI work? If not, any error displayed? If it does work, what's the error from the installer you're getting?

No, the web UI does not work.

Same questions.. is any error displayed when you access the web UI? Any logging? What's the error from the installer? There isn't enough information here to know what the problem you're experiencing is caused by.

Please also try with SELinux set to permission (setenforce 0).

Which mode is SELinux in (sestatus, getenforce)? There is a bug report for AVCs due to a mislabel when it is enforcing (#14811).

I just came across this myself in RHEL 7.2. Though I got some weird results. Will work to isolate here in a minute.

Web UI:
Web UI comes up, and can login with default admin credentials shown during foreman-install
No Apache error logs are updated when trying to hit the web ui.
Web UI looks ok, but no Smart Proxies are registered

SELinux:
Initial install was performed in enforcing more. Switching to permissive and re-running foreman-install reported no errors, and smart proxy appears in web UI?
Will reset lab VM and re-install w/ SELinux in permissive...

Errors during Install

[root@deploy foreman-installer]# grep ERROR foreman.*
foreman.1.log:[DEBUG 2016-04-26 08:45:32 main] calling :function_validate_re with [["ERROR", "^(UNKNOWN|FATAL|ERROR|WARN|INFO|DEBUG)$"]]
foreman.1.log:[ERROR 2016-04-26 08:46:00 main]  /Stage[main]/Foreman_proxy::Register/Foreman_smartproxy[deploy.lab]: Could not evaluate: Proxy deploy.lab cannot be registered (Could not load data from https://deploy.lab
foreman.1.log:[ERROR 2016-04-26 08:46:05 main] Errors encountered during run:
foreman.1.log:[ERROR 2016-04-26 08:46:05 main]  /Stage[main]/Foreman_proxy::Register/Foreman_smartproxy[deploy.lab]: Could not evaluate: Proxy deploy.lab cannot be registered (Could not load data from https://deploy.lab
foreman.2.log:[DEBUG 2016-04-25 16:58:32 main] calling :function_validate_re with [["ERROR", "^(UNKNOWN|FATAL|ERROR|WARN|INFO|DEBUG)$"]]
foreman.2.log:[ INFO 2016-04-25 17:09:33 main]  # WARN, DEBUG, ERROR, FATAL, INFO, UNKNOWN
foreman.2.log:[ INFO 2016-04-25 17:09:33 main] -#:log_level: ERROR
foreman.2.log:[ INFO 2016-04-25 17:09:33 main] +:log_level: ERROR
foreman.2.log:[ERROR 2016-04-25 17:12:54 main]  /Stage[main]/Foreman_proxy::Register/Foreman_smartproxy[deploy.lab]: Could not evaluate: Proxy deploy.lab cannot be registered (Could not load data from https://deploy.lab
foreman.2.log:[ERROR 2016-04-25 17:12:58 main]  /Stage[main]/Foreman_proxy::Register/Foreman_smartproxy[deploy.lab]: Failed to call refresh: Proxy deploy.lab cannot be registered (Could not load data from https://deploy.lab
foreman.2.log:[ERROR 2016-04-25 17:12:58 main]  /Stage[main]/Foreman_proxy::Register/Foreman_smartproxy[deploy.lab]: Proxy deploy.lab cannot be registered (Could not load data from https://deploy.lab
foreman.log:[DEBUG 2016-04-26 08:46:25 main] calling :function_validate_re with [["ERROR", "^(UNKNOWN|FATAL|ERROR|WARN|INFO|DEBUG)$"]]
foreman.log:[ERROR 2016-04-26 08:46:52 main]  /Stage[main]/Foreman_proxy::Register/Foreman_smartproxy[deploy.lab]: Could not evaluate: Proxy deploy.lab cannot be registered (Could not load data from https://deploy.lab

RPM Package Versions:

[root@deploy httpd]# rpm -qa | grep passenger
passenger-4.0.53-4.el7.x86_64
mod_passenger-4.0.53-4.el7.x86_64
tfm-rubygem-passenger-4.0.18-9.10.el7.x86_64
tfm-rubygem-passenger-native-4.0.18-9.10.el7.x86_64
tfm-rubygem-passenger-native-libs-4.0.18-9.10.el7.x86_64

Is there any other logging you need?

David Gersting wrote:

SELinux:
Initial install was performed in enforcing more. Switching to permissive and re-running foreman-install reported no errors, and smart proxy appears in web UI?
Will reset lab VM and re-install w/ SELinux in permissive...

Thanks, your problem is almost certainly ticket #14811. A fix is in progress.

As you found, changing SELinux to permissive will fix it or perhaps prioritising the Foreman repo over EPEL (our repo has an older version of Passenger that has SELinux support).

I see the same. I just reset my lab VM, and foreman-install runs cleanly when SELinux is in Permissive mode. There's still the errors about the Ruby version in Apache's error_log, but the daemon starts and nothing seems broken. (but I've also not tested anything other than the install itself)