Project

General

Profile

Actions

Bug #10238

open

"--no-enable-puppet" breaks foreman-installer

Added by Sebastiaan Glazenborg almost 9 years ago. Updated almost 9 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

Description

Trying to test foreman using Saltstack instead of puppet.

OS: CentOS 7.1

Foreman:
Version : 1.8.0
Release : 0.1.RC3.el7

[root@foreman1 ~]# foreman-installer \
 --no-enable-puppet \
 --enable-foreman-plugin-salt
 Could not start Service[foreman-proxy]: Execution of '/usr/bin/systemctl start foreman-proxy' returned 1: Job for foreman-proxy.service failed. See 'systemctl status foreman-proxy.service' and 'journalctl -xn' for details.
 /Stage[main]/Foreman_proxy::Service/Service[foreman-proxy]/ensure: change from stopped to running failed: Could not start Service[foreman-proxy]: Execution of '/usr/bin/systemctl start foreman-proxy' returned 1: Job for foreman-proxy.service failed. See 'systemctl status foreman-proxy.service' and 'journalctl -xn' for details.
 Could not start Service[httpd]: Execution of '/usr/bin/systemctl start httpd' returned 1: Job for httpd.service failed. See 'systemctl status httpd.service' and 'journalctl -xn' for details.
 /Stage[main]/Apache::Service/Service[httpd]/ensure: change from stopped to running failed: Could not start Service[httpd]: Execution of '/usr/bin/systemctl start httpd' returned 1: Job for httpd.service failed. See 'systemctl status httpd.service' and 'journalctl -xn' for details.
 /Stage[main]/Foreman_proxy::Register/Foreman_smartproxy[foreman1.domain.local]: Failed to call refresh: Could not load data from https://foreman1.domain.local
 /Stage[main]/Foreman_proxy::Register/Foreman_smartproxy[foreman1.domain.local]: Could not load data from https://foreman1.domain.local
[root@foreman1 foreman]# systemctl status httpd.service

Apr 22 11:24:38 foreman1.domain.local httpd[6255]: SSLCertificateFile: file '/var/lib/puppet/ssl/certs/foreman1.domain.local.pem' does not exist or is empty
[root@foreman1 foreman]# ll /var/lib/puppet/ssl/certs/
total 0

Related issues 1 (0 open1 closed)

Blocked by Installer - Tracker #10161: Support Multiple Installation ScenariosResolved04/16/2015

Actions
Actions #1

Updated by Dominic Cleal almost 9 years ago

  • Project changed from Foreman to Installer

Yeah, this is expected as the default SSL configuration relies on Puppet's certificate authority. It'd be possible to figure out and document a couple of scenarios, a) using your own certificate(s), b) no SSL configuration.

Actions #2

Updated by Sebastiaan Glazenborg almost 9 years ago

Ok; so instead of a bug this should be a feature request?

c) change the dependency; not rely on Puppet generated SSL files?

For my info: "a) using your own certificate(s)" you are referring to these options correct?

--foreman-server-ssl-ca
--foreman-server-ssl-cert
--foreman-server-ssl-chain
--foreman-server-ssl-crl
--foreman-server-ssl-key

--foreman-proxy-ssl-ca
--foreman-proxy-ssl-cert
--foreman-proxy-ssl-key
--foreman-proxy-ssldir

Actions #3

Updated by Dominic Cleal almost 9 years ago

Yes.

Actions #4

Updated by Stephen Benjamin almost 9 years ago

  • Blocked by Tracker #10161: Support Multiple Installation Scenarios added
Actions

Also available in: Atom PDF