Support #19725
closedForeman installation error
Description
Description of the problem:
The following errors were observed during the installation of Foreman,
1) Execution of '/bin/yum -d 0 -e 0 -y install foreman-postgresql' returned 1: Removing tfm-rubygem-foreigner.noarch 0:1.7.1-3.el7 - u due to obsoletes from installed tfm-runtime-3.2-5.el7.x86_64
Removing tfm-rubygem-sprockets.noarch 0:3.5.2-1.el7 - u due to obsoletes from installed tfm-runtime-3.2-5.el7.x86_64
Removing tfm-rubygem-sprockets-rails.noarch 0:2.3.3-1.el7 - u due to obsoletes from installed tfm-runtime-3.2-5.el7.x86_64
Removing tfm-rubygem-turbolinks.noarch 0:2.5.3-3.el7 - u due to obsoletes from installed tfm-runtime-3.2-5.el7.x86_64
2) Execution of '/bin/yum -d 0 -e 0 -y install puppet-server' returned 1: Package puppet-3.8.6-1.el7.noarch is obsoleted by puppet-agent-1.8.2-1.el7.x86_64 which is already installed
Foreman version:
0.84.0
OS:
Centos 7
Additional Info:
The following log messages were also found in the installer logs,
1) Could not find a suitable provider for foreman_config_entry
2) Could not find a suitable provider for foreman_smartproxy
Updated by Dominic Cleal almost 7 years ago
1) The root error isn't shown, run "yum install foreman-postgresql" and look at/provide the full error message.
2) It looks like you are mixing repositories or answers files. It might be that the installer has been run with Puppet 3 and then you've upgraded to Puppet 4 (puppet-agent), which won't work - either use the upgrade instructions to update the installer configuration to match or reinstall.
Additional errors are hard to diagnose without the log file. It might simply be a consequence of the earlier errors that they occur.