Not able to install Foreman 1.12 on RHEL 7.2

Support
#1

I followed the instruction to install Foreman 1.12 on RHEL 7.2.

foreman-installer

Execution of '/bin/yum -d 0 -e 0 -y install foreman-proxy' returned 1:
Error: Package: foreman-proxy-1.12.1-1.el7.noarch (foreman)
/Stage[main]/Foreman_proxy::Install/Package[foreman-proxy]/ensure: change
from purged to present failed: Execution of '/bin/yum -d 0 -e 0 -y install
foreman-proxy' returned 1: Error: Package:
foreman-proxy-1.12.1-1.el7.noarch (foreman)
Execution of '/bin/yum -d 0 -e 0 -y install mod_passenger' returned 1:
Error: Package: passenger-4.0.53-4.el7.x86_64 (epel)
/Stage[main]/Apache::Mod::Passenger/Apache::Mod[passenger]/Package[mod_passenger]/ensure:
change from purged to present failed: Execution of '/bin/yum -d 0 -e 0 -y
install mod_passenger' returned 1: Error: Package:
passenger-4.0.53-4.el7.x86_64 (epel)
Installing Done
[100%] […]
Something went wrong! Check the log for ERROR-level output

What can be the reason? lsof could not find 8443 is up.

uname -a

Linux for01 3.10.0-327.el7.x86_64 #1 SMP Fri Nov 20 00:18:34 PST 2015
x86_64 x86_64 x86_64 GNU/Linux

#2

No, the package installation failed. Run the commands having a problem
(yum install foreman-proxy) and check the output for more information.

Ensure you have the RHEL "optional" repository enabled.

··· On 18/08/16 21:12, Victor Feng wrote: > I followed the instruction to install Foreman 1.12 on RHEL 7.2. > > # foreman-installer > Execution of '/bin/yum -d 0 -e 0 -y install foreman-proxy' returned 1: > Error: Package: foreman-proxy-1.12.1-1.el7.noarch (foreman) > /Stage[main]/Foreman_proxy::Install/Package[foreman-proxy]/ensure: > change from purged to present failed: Execution of '/bin/yum -d 0 -e 0 > -y install foreman-proxy' returned 1: Error: Package: > foreman-proxy-1.12.1-1.el7.noarch (foreman) > Execution of '/bin/yum -d 0 -e 0 -y install mod_passenger' returned 1: > Error: Package: passenger-4.0.53-4.el7.x86_64 (epel) > /Stage[main]/Apache::Mod::Passenger/Apache::Mod[passenger]/Package[mod_passenger]/ensure: > change from purged to present failed: Execution of '/bin/yum -d 0 -e 0 > -y install mod_passenger' returned 1: Error: Package: > passenger-4.0.53-4.el7.x86_64 (epel) > Installing Done > [100%] [...............................] > Something went wrong! Check the log for ERROR-level output > * Foreman is running at https://for01.domain.com > Initial credentials are admin / 6izVgbykNsrhXVYE > * Foreman Proxy is running at https://for01.domain.com:8443 > * Puppetmaster is running at port 8140 > The full log is at /var/log/foreman-installer/foreman.log > > What can be the reason? lsof could not find 8443 is up.

–
Dominic Cleal
dominic@cleal.org

#3

>
> Thank you Dominic. After adding "Optional" repository, the problem was
> resolved. But at end of installation, it gave
>
/Stage[main]/Foreman_proxy::Register/Foreman_smartproxy[seidevfor03.gwpdev.seic.com]:
Could not evaluate: Exception Connection refused - connect(2) for
"seidevfor03.gwpdev.seic.com" port 443 in get request to:
https://seidevfor03.gwpdev.seic.com/api/v2/smart_proxies?search=name="seidevfor03.gwpdev.seic.com"
/Stage[main]/Foreman_proxy::Register/Foreman_smartproxy[seidevfor03.gwpdev.seic.com]:
Failed to call refresh: Exception Connection refused - connect(2) for
"seidevfor03.gwpdev.seic.com" port 443 in get request to:
https://seidevfor03.gwpdev.seic.com/api/v2/smart_proxies?search=name="seidevfor03.gwpdev.seic.com"
/Stage[main]/Foreman_proxy::Register/Foreman_smartproxy[seidevfor03.gwpdev.seic.com]:
Exception Connection refused - connect(2) for "seidevfor03.gwpdev.seic.com"
port 443 in get request to:
https://seidevfor03.gwpdev.seic.com/api/v2/smart_proxies?search=name="seidevfor03.gwpdev.seic.com"
Installing Done
[100%] […]
Something went wrong! Check the log for ERROR-level output

systemctl status puppetserver shows puppet server is running. admin is able
to log into Foreman.

root@seidevfor03# puppet agent -t
Warning: Unable to fetch my node definition, but the agent run will
continue:
Warning: Find
/puppet/v3/node/seidevfor03.gwpdev.seic.com?environment=production&configured_environment=product…
resulted in 404 with the message: {"message":"Not Found: Could not find
node seidevfor03.gwpdev.seic.com","issue_kind":"RESOURCE_NOT_FOUND"}
Info: Retrieving pluginfacts
Info: Retrieving plugin
Error: Could not retrieve catalog from remote server: Error 500 on SERVER:
Server Error: Could not find node 'seidevfor03.gwpdev.seic.com'; cannot
compile
Warning: Not using cache on failed catalog
Error: Could not retrieve catalog; skipping run
root@seidevfor03#

Looks like it is using Puppet 3 instead 4? /usr/bin/puppet does not exit,
so I added /opt/puppetlabs/bin to PATH.

Here is the installation log
root@seidevfor03# cat /var/log/puppetlabs/puppetserver/puppetserver.log
2016-08-19 10:49:19,373 WARN [main] [p.t.bootstrap] Duplicate bootstrap
entry found for service
'puppetlabs.services.ca.certificate-authority-service/certificate-authority-service'
on line number '2' in file '/etc/puppetlabs/puppetserver/services.d/ca.cfg'
2016-08-19 10:49:19,377 WARN [main] [p.t.bootstrap] Duplicate bootstrap
entry found for service
'puppetlabs.services.versioned-code-service.versioned-code-service/versioned-code-service'
on line number '12' in file
'/opt/puppetlabs/server/apps/puppetserver/config/services.d/bootstrap.cfg'
2016-08-19 10:49:23,526 INFO [main] [o.e.j.u.log] Logging initialized
@11519ms
2016-08-19 10:49:24,632 INFO [async-dispatch-2]
[p.s.j.jruby-puppet-service] Initializing the JRuby service
2016-08-19 10:49:24,647 INFO [async-dispatch-2]
[p.s.j.jruby-pool-manager-service] Initializing the JRuby service
2016-08-19 10:49:24,659 INFO [async-dispatch-2] [p.t.s.w.jetty9-service]
Initializing web server(s).
2016-08-19 10:49:24,675 INFO [clojure-agent-send-pool-0]
[p.s.j.i.jruby-internal] Creating JRubyInstance with id 1.
2016-08-19 10:49:37,032 WARN [clojure-agent-send-pool-0] [puppetserver]
Puppet Comparing Symbols to non-Symbol values is deprecated
(file & line not available)
2016-08-19 10:49:37,090 INFO [clojure-agent-send-pool-0] [puppetserver]
Puppet Puppet settings initialized; run mode: master
2016-08-19 10:49:37,539 INFO [clojure-agent-send-pool-0]
[p.s.j.i.jruby-agents] Finished creating JRubyInstance 1 of 2
2016-08-19 10:49:37,540 INFO [clojure-agent-send-pool-0]
[p.s.j.i.jruby-internal] Creating JRubyInstance with id 2.
2016-08-19 10:49:37,588 INFO [async-dispatch-2]
[p.s.c.puppet-server-config-core] Not overriding webserver settings with
values from core Puppet
2016-08-19 10:49:37,618 WARN [async-dispatch-2]
[p.p.certificate-authority] The 'client-whitelist' and
'authorization-required' settings in the
'certificate-authority.certificate-status' section are deprecated and will
be removed in a future release. Remove these settings and create an
appropriate authorization rule in the
/etc/puppetlabs/puppetserver/conf.d/auth.conf file.
2016-08-19 10:49:37,620 INFO [async-dispatch-2]
[p.p.certificate-authority] CA already initialized for SSL
2016-08-19 10:49:37,623 INFO [async-dispatch-2]
[p.s.c.certificate-authority-service] CA Service adding a ring handler
2016-08-19 10:49:37,660 INFO [async-dispatch-2]
[p.s.v.versioned-code-service] No code-id-command set for
versioned-code-service. Code-id will be nil.
2016-08-19 10:49:37,660 INFO [async-dispatch-2]
[p.s.v.versioned-code-service] No code-content-command set for
versioned-code-service. Attempting to fetch code content will fail.
2016-08-19 10:49:37,736 WARN [async-dispatch-2] [o.e.j.s.h.ContextHandler]
Empty contextPath
2016-08-19 10:49:37,791 INFO [async-dispatch-2]
[p.p.certificate-authority] Master already initialized for SSL
2016-08-19 10:49:37,791 INFO [async-dispatch-2] [p.s.m.master-service]
Master Service adding ring handlers
2016-08-19 10:49:37,794 INFO [async-dispatch-2]
[p.s.p.puppet-admin-service] Starting Puppet Admin web app
2016-08-19 10:49:37,796 WARN [async-dispatch-2]
[p.s.p.puppet-admin-service] The 'client-whitelist' and
'authorization-required' settings in the 'puppet-admin' section are
deprecated and will be removed in a future release. Remove these settings
and create an appropriate authorization rule in the
/etc/puppetlabs/puppetserver/conf.d/auth.conf file.
2016-08-19 10:49:37,800 INFO [async-dispatch-2] [p.t.s.w.jetty9-service]
Starting web server(s).
2016-08-19 10:49:38,429 INFO [async-dispatch-2] [p.t.s.w.jetty9-core]
Starting web server.
2016-08-19 10:49:38,431 INFO [async-dispatch-2] [o.e.j.s.Server]
jetty-9.2.z-SNAPSHOT
2016-08-19 10:49:38,504 INFO [async-dispatch-2] [o.e.j.s.h.ContextHandler]
Started o.e.j.s.h.ContextHandler@9119b50{/puppet-ca,null,AVAILABLE}
2016-08-19 10:49:38,504 INFO [async-dispatch-2] [o.e.j.s.h.ContextHandler]
Started o.e.j.s.h.ContextHandler@4bc52da1{/,null,AVAILABLE}
2016-08-19 10:49:38,505 INFO [async-dispatch-2] [o.e.j.s.h.ContextHandler]
Started o.e.j.s.h.ContextHandler@635f6d4e{/puppet,null,AVAILABLE}
2016-08-19 10:49:38,505 INFO [async-dispatch-2] [o.e.j.s.h.ContextHandler]
Started o.e.j.s.h.ContextHandler@327e16d4{/puppet-admin-api,null,AVAILABLE}
2016-08-19 10:49:38,620 INFO [async-dispatch-2] [o.e.j.s.ServerConnector]
Started ServerConnector@35ed4083{SSL-HTTP/1.1}{0.0.0.0:8140}
2016-08-19 10:49:38,620 INFO [async-dispatch-2] [o.e.j.s.Server] Started
@26614ms
2016-08-19 10:49:38,624 INFO [async-dispatch-2]
[p.s.l.legacy-routes-service] The legacy routing service has successfully
started and is now ready to handle requests
2016-08-19 10:49:38,625 INFO [async-dispatch-2] [p.s.m.master-service]
Puppet Server has successfully started and is now ready to handle requests
2016-08-19 10:49:40,264 WARN [clojure-agent-send-pool-0] [puppetserver]
Puppet Comparing Symbols to non-Symbol values is deprecated
(file & line not available)
2016-08-19 10:49:40,281 INFO [clojure-agent-send-pool-0] [puppetserver]
Puppet Puppet settings initialized; run mode: master
2016-08-19 10:49:40,541 INFO [clojure-agent-send-pool-0]
[p.s.j.i.jruby-agents] Finished creating JRubyInstance 2 of 2

#4

It is resolved after re-run foreman-installer
–enable-foreman-compute-libvirt

https://groups.google.com/forum/#!topic/foreman-users/-bA3HGTHy5M

··· On Friday, August 19, 2016 at 2:13:52 AM UTC-4, Victor Feng wrote: > > I followed the instruction to install Foreman 1.12 on RHEL 7.2. > > # foreman-installer > Execution of '/bin/yum -d 0 -e 0 -y install foreman-proxy' returned 1: > Error: Package: foreman-proxy-1.12.1-1.el7.noarch (foreman) > /Stage[main]/Foreman_proxy::Install/Package[foreman-proxy]/ensure: change > from purged to present failed: Execution of '/bin/yum -d 0 -e 0 -y install > foreman-proxy' returned 1: Error: Package: > foreman-proxy-1.12.1-1.el7.noarch (foreman) > Execution of '/bin/yum -d 0 -e 0 -y install mod_passenger' returned 1: > Error: Package: passenger-4.0.53-4.el7.x86_64 (epel) > /Stage[main]/Apache::Mod::Passenger/Apache::Mod[passenger]/Package[mod_passenger]/ensure: > change from purged to present failed: Execution of '/bin/yum -d 0 -e 0 -y > install mod_passenger' returned 1: Error: Package: > passenger-4.0.53-4.el7.x86_64 (epel) > Installing Done > [100%] [...............................] > Something went wrong! Check the log for ERROR-level output > * Foreman is running at https://for01.domain.com > Initial credentials are admin / 6izVgbykNsrhXVYE > * Foreman Proxy is running at https://for01.domain.com:8443 > * Puppetmaster is running at port 8140 > The full log is at /var/log/foreman-installer/foreman.log > > What can be the reason? lsof could not find 8443 is up. > > # uname -a > Linux for01 3.10.0-327.el7.x86_64 #1 SMP Fri Nov 20 00:18:34 PST 2015 > x86_64 x86_64 x86_64 GNU/Linux > > >