Actions
Bug #10238
open"--no-enable-puppet" breaks foreman-installer
Status:
New
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
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
Actions