Bug #2442
closed
Foreman Installer requires puppet-server when it shouldn't. HTTP won't start, either.
Added by Matthew Barr about 11 years ago.
Updated almost 6 years ago.
Description
Using Centos 6.4:
foreman-1.1stable-3.el6.noarch
foreman-proxy-1.1stable-1.el6.noarch
foreman-release-1.1stable-3.el6.noarch
foreman-installer-1.1.1-1.noarch
foreman-sqlite-1.1stable-3.el6.noarch
and an answers file of:
---
puppet: false
foreman_proxy:
dhcp: true
puppetca: false
puppetrun: false
puppetmaster: false
foreman: true
I see the installer try to install puppet-server, (only once, though.)
The puppet-server dependency doesn't seem to persist into the 2nd run, manually, but the following does:
Fail to start httpd, due to the presence of :
/etc/httpd/conf.d/puppet.conf
(it has the SSL keys in that conf, so that http fails.)
- Project changed from Foreman to Installer
- Priority changed from Normal to High
- Target version set to 27
- Status changed from New to Feedback
Can you confirm the path of the answers file you edited please?
/usr/share/foreman-installer/foreman_installer/answers.yaml
And it was the output of the installer script,
ruby /usr/share/foreman-installer/generate_answers.rb
Not edited by hand.
- Status changed from Feedback to Assigned
- Assignee set to Greg Sutcliffe
- Priority changed from High to Urgent
Greg's figured this out and pushed a fix, we'll update the 1.1 installer too as it's severe. Thanks for the report!
It was an ordering issue where if you selected "yes" to run Puppet immediately in the installer, it would run Puppet and then write out the answers file, so it would do the Puppet run using the default options. If you selected "no", it would just write out the file and then give you the command to run Puppet.
- Status changed from Assigned to Resolved
foreman-installer 1.1.2 has been released with the patch.
- Target version changed from 27 to 1.2.0
- Target version deleted (
1.2.0)
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by