Impossible to install foreman-proxy

Hi,

I tried to do a fresh install of Foreman 3.0.1 with Katello on a CentOS 8, it worked well. Then i tried to install an external Foreman Proxy 3.0.1 on a CentOS 8 also but i got some issues.
I follow the official documentation Installing an External Smart Proxy Server 3.0.

Problem:

When i do a foreman-installer i had the errors bellow :

2021-12-17 14:30:24 [ERROR ] [configure] Evaluation Error: Error while evaluating a Resource Statement, Foreman::Plugin[puppet]:
2021-12-17 14:30:24 [ERROR ] [configure] parameter 'version' expects a String value, got Undef
2021-12-17 14:30:24 [ERROR ] [configure] parameter 'config_file_group' expects a String value, got Undef (file: /usr/share/foreman-installer/modules/foreman/manifests/plugin/puppet.pp, line: 6) on node new-foreman-proxy-fon.interne.mines-paristech.fr

I tried the solution proposed on the post Foreman installer error "parameter 'version' expects a String value, got Undef" (adding --no-enable-foreman-plugin-puppet and --no-enable-foreman-cli-puppet) but i got other errors :

2021-12-17 15:05:24 [ERROR ] [configure] Systemd start for puppetserver failed!
2021-12-17 15:05:24 [ERROR ] [configure] journalctl log for puppetserver:
2021-12-17 15:05:24 [ERROR ] [configure] -- Logs begin at Fri 2021-12-10 14:35:24 CET, end at Fri 2021-12-17 15:05:24 CET. --
2021-12-17 15:05:24 [ERROR ] [configure] Dec 17 15:04:42 test-aurel.interne.mines-paristech.fr systemd[1]: Starting puppetserver Service...
2021-12-17 15:05:24 [ERROR ] [configure] Dec 17 15:05:23 test-aurel.interne.mines-paristech.fr puppetserver[102594]: Execution error (IllegalArgumentException) at puppetlabs.trapperkeeper.services.webserver.jetty9-config/fn$get-x509s-from-ssl-cert-pem$fn (jetty9_config.clj:246).
2021-12-17 15:05:24 [ERROR ] [configure] Dec 17 15:05:23 test-aurel.interne.mines-paristech.fr puppetserver[102594]: Unable to open 'ssl-cert' file: /etc/puppetlabs/puppet/ssl/certs/test-aurel.interne.mines-paristech.fr.pem
2021-12-17 15:05:24 [ERROR ] [configure] Dec 17 15:05:23 test-aurel.interne.mines-paristech.fr puppetserver[102594]: Full report at:

Expected outcome:

An installation without errors

Foreman and Proxy versions:

foreman-release-3.0.1-1.el8.noarch
foreman-proxy-3.0.1-1.el8.noarch

Foreman and Proxy plugin versions:

[root@test-aurel ~]rpm -qa |grep foreman
foreman-installer-3.0.1-1.el8.noarch
foreman-proxy-3.0.1-1.el8.noarch
foreman-release-3.0.1-1.el8.noarch
foreman-debug-3.0.1-1.el8.noarch

Distribution and version:

CentOS Linux release 8.5.2111

Other relevant data:

Here is the complete set of commands used to install the proxy (following the documentation mentioned before):

dnf clean all
dnf localinstall -y https://yum.theforeman.org/releases/3.0/el8/x86_64/foreman-release.rpm
dnf localinstall -y https://yum.puppet.com/puppet6-release-el-8.noarch.rpm
dnf module reset ruby
dnf module -y enable ruby:2.7
dnf module -y enable postgresql:12
dnf -y update
dnf install foreman-installer

foreman-installer \
  --no-enable-foreman \
  --no-enable-foreman-cli \
  --enable-puppet \
  --puppet-server-ca=false \
  --puppet-server-foreman-url=https://foreman.XXXXXXXX.fr \
  --enable-foreman-proxy \
  --foreman-proxy-puppetca=false \
  --foreman-proxy-tftp=false \
  --foreman-proxy-foreman-base-url=https://foreman.XXXXXXXX.fr \
  --foreman-proxy-trusted-hosts=foreman.XXXXXXXX.fr \
  --foreman-proxy-oauth-consumer-key=xxxxx \
  --foreman-proxy-oauth-consumer-secret=xxxxxxx
1 Like

HI,

Have you managed to correct these errors? Im encountering the same error as well. Thanks.

Are you also installing foreman 3.0.1? If so, you should rather install the latest version. If not, I’d doubt it’s really the identical error you get…

Im installing the newest version. Here is the error I’m getting.

2022-11-07 12:12:59 [NOTICE] [configure] Starting system configuration.
2022-11-07 12:13:07 [NOTICE] [configure] 250 configuration steps out of 671 steps complete.
2022-11-07 12:13:22 [ERROR ] [configure] Systemd start for puppetserver failed!
2022-11-07 12:13:22 [ERROR ] [configure] journalctl log for puppetserver:
2022-11-07 12:13:22 [ERROR ] [configure] – Logs begin at Fri 2022-11-04 14:52:15 +08, end at Mon 2022-11-07 12:13:22 +08. –
2022-11-07 12:13:22 [ERROR ] [configure] Nov 07 12:08:28 nestor.url3.net puppetserver[52232]: Execution error (IllegalArgumentException) at puppetlabs.trapperkeeper.services.webserver.jetty9-config/fn$get-x509s-from-ssl-cert-pem$fn (jetty9_config.clj:246).
2022-11-07 12:13:22 [ERROR ] [configure] Nov 07 12:08:28 nestor.url3.net puppetserver[52232]: Unable to open ‘ssl-cert’ file: /etc/puppetlabs/puppet/ssl/certs/nestor.url3.net.pem
2022-11-07 12:13:22 [ERROR ] [configure] Nov 07 12:08:28 nestor.url3.net puppetserver[52232]: Full report at:
2022-11-07 12:13:22 [ERROR ] [configure] Nov 07 12:08:28 nestor.url3.net puppetserver[52232]: /tmp/clojure-2284044438582669856.edn
2022-11-07 12:13:22 [ERROR ] [configure] Nov 07 12:08:29 nestor.url3.net systemd[1]: puppetserver.service: Control process exited, code=exited status=1
2022-11-07 12:13:22 [ERROR ] [configure] Nov 07 12:08:29 nestor.url3.net systemd[1]: puppetserver.service: Failed with result ‘exit-code’.
2022-11-07 12:13:22 [ERROR ] [configure] Nov 07 12:08:29 nestor.url3.net systemd[1]: Failed to start puppetserver Service.
2022-11-07 12:13:22 [ERROR ] [configure] Nov 07 12:08:29 nestor.url3.net systemd[1]: puppetserver.service: Service RestartSec=100ms expired, scheduling restart.
2022-11-07 12:13:22 [ERROR ] [configure] Nov 07 12:08:29 nestor.url3.net systemd[1]: puppetserver.service: Scheduled restart job, restart counter is at 31.
2022-11-07 12:13:22 [ERROR ] [configure] Nov 07 12:08:29 nestor.url3.net systemd[1]: Stopped puppetserver Service.
2022-11-07 12:13:22 [ERROR ] [configure] Nov 07 12:08:29 nestor.url3.net systemd[1]: Starting puppetserver Service…
2022-11-07 12:13:22 [ERROR ] [configure] Nov 07 12:08:33 nestor.url3.net puppetserver[52472]: WARNING: abs already refers to: #'clojure.core/abs in namespace: medley.core, being replaced by: #'medley.core/abs
2022-11-07 12:13:22 [NOTICE] [configure] 500 configuration steps out of 671 steps complete.
2022-11-07 12:13:23 [ERROR ] [configure] Systemd start for foreman-proxy failed!
2022-11-07 12:13:23 [ERROR ] [configure] journalctl log for foreman-proxy:
2022-11-07 12:13:23 [ERROR ] [configure] – Logs begin at Fri 2022-11-04 14:52:15 +08, end at Mon 2022-11-07 12:13:23 +08. –
2022-11-07 12:13:23 [ERROR ] [configure] Nov 07 12:10:56 nestor.url3.net systemd[1]: Starting Foreman Proxy…
2022-11-07 12:13:23 [ERROR ] [configure] Nov 07 12:10:57 nestor.url3.net systemd[1]: foreman-proxy.service: Main process exited, code=exited, status=1/FAILURE
2022-11-07 12:13:23 [ERROR ] [configure] Nov 07 12:10:57 nestor.url3.net systemd[1]: foreman-proxy.service: Failed with result ‘exit-code’.
2022-11-07 12:13:23 [ERROR ] [configure] Nov 07 12:10:57 nestor.url3.net systemd[1]: Failed to start Foreman Proxy.
2022-11-07 12:13:23 [ERROR ] [configure] Nov 07 12:13:22 nestor.url3.net systemd[1]: Starting Foreman Proxy…
2022-11-07 12:13:23 [ERROR ] [configure] Nov 07 12:13:23 nestor.url3.net systemd[1]: foreman-proxy.service: Main process exited, code=exited, status=1/FAILURE
2022-11-07 12:13:23 [ERROR ] [configure] Nov 07 12:13:23 nestor.url3.net systemd[1]: foreman-proxy.service: Failed with result ‘exit-code’.
2022-11-07 12:13:23 [ERROR ] [configure] Nov 07 12:13:23 nestor.url3.net systemd[1]: Failed to start Foreman Proxy.
2022-11-07 12:13:23 [ERROR ] [configure] /Stage[main]/Foreman_proxy::Service/Service[foreman-proxy]/ensure: change from ‘stopped’ to ‘running’ failed: Systemd start for foreman-proxy failed!
2022-11-07 12:13:23 [ERROR ] [configure] journalctl log for foreman-proxy:
2022-11-07 12:13:23 [ERROR ] [configure] – Logs begin at Fri 2022-11-04 14:52:15 +08, end at Mon 2022-11-07 12:13:23 +08. –
2022-11-07 12:13:23 [ERROR ] [configure] Nov 07 12:10:56 nestor.url3.net systemd[1]: Starting Foreman Proxy…
2022-11-07 12:13:23 [ERROR ] [configure] Nov 07 12:10:57 nestor.url3.net systemd[1]: foreman-proxy.service: Main process exited, code=exited, status=1/FAILURE
2022-11-07 12:13:23 [ERROR ] [configure] Nov 07 12:10:57 nestor.url3.net systemd[1]: foreman-proxy.service: Failed with result ‘exit-code’.
2022-11-07 12:13:23 [ERROR ] [configure] Nov 07 12:10:57 nestor.url3.net systemd[1]: Failed to start Foreman Proxy.
2022-11-07 12:13:23 [ERROR ] [configure] Nov 07 12:13:22 nestor.url3.net systemd[1]: Starting Foreman Proxy…
2022-11-07 12:13:23 [ERROR ] [configure] Nov 07 12:13:23 nestor.url3.net systemd[1]: foreman-proxy.service: Main process exited, code=exited, status=1/FAILURE
2022-11-07 12:13:23 [ERROR ] [configure] Nov 07 12:13:23 nestor.url3.net systemd[1]: foreman-proxy.service: Failed with result ‘exit-code’.
2022-11-07 12:13:23 [ERROR ] [configure] Nov 07 12:13:23 nestor.url3.net systemd[1]: Failed to start Foreman Proxy.
2022-11-07 12:13:24 [NOTICE] [configure] System configuration has finished.

These are the commands Im using,

foreman-installer
–no-enable-foreman
–no-enable-foreman-cli-puppet
–no-enable-foreman-plugin-puppet
–puppet-server-ca=false
–puppet-server-foreman-url=https://tomtit.url3.net
–enable-foreman-proxy
–foreman-proxy-puppetca=false
–foreman-proxy-tftp=false
–foreman-proxy-foreman-base-url=https://tomtit.url3.net
–foreman-proxy-trusted-hosts=
–foreman-proxy-oauth-consumer-key=
–foreman-proxy-oauth-consumer-secret=

So you don’t get the initial error. You should rather start a new thread and give all the information required. If you install the content proxy following the latest docs it shouldn’t install the puppetserver at all…

I got the initial error as well. I just followed some of the solutions found here in the forum then ended up with the error above. I followed this guide from the docs; [Installing an External Smart Proxy Server nightly (theforeman.org)](Installing an External Smart Proxy Server nightly. This is the latest one right? Thanks.

Again: You should rather start a new thread and give all the information required. A lot has happened between 3.0/4.2 and 3.4/4.6. You should also use the release docs and not the nightly…