Project

General

Profile

FAQ » History » Version 62

Version 61 (Dominic Cleal, 09/24/2014 09:34 AM) → Version 62/68 (Dominic Cleal, 02/04/2015 10:47 AM)

{{toc}}

h1. Common Issues

h2. I can't login with the 'admin' account and 'rake permissions:reset' gives me an error.

Your account was created without an FQDN email address. Login to your SQL server and run "update users set mail='admin@example.com' where login='admin';"

h2. I'm getting a 400 from my foreman-proxy when trying to:

h3. Allocate DHCP addresses.

Make sure both dhcpd.conf and the dhcp leases file are both readable by your foreman-proxy user.

h3. Run Puppet CA

Puppet needs special sudo permissions. Pay close attention to the manual at this section - http://theforeman.org/manuals/1.2/index.html#4.3.2SmartProxySettings - specifically, "Puppet Certificate Authority Section".



h1. Other FAQ

h2. Does Foreman support Puppet 4?

Support for Puppet 4 needs a lot of work, especially due to the AIO packaging changes, work on updating installer modules etc. Please join the foreman-dev list/IRC channel if you're interested in helping!

h2. Does Foreman support Puppet
3?

Support for Puppet 3 has been added in Foreman 1.1 (proxy and web UI). The [[PuppetThreeWorkarounds]] page has additional details about pre-1.1 issues. details.

h2. Upgrade puppet from v2 to v3 gotchas

/etc/sudoers.d/foreman-proxy still contains the old puppet commands which will cause the provision URL not to work, errors will be in /var/log/foreman-proxy/proxy.log about sudo failing, error in /var/log/foreman/production.log is about Failed to remove hosts.domain.com's puppet certificate: 406 Not Acceptable. Solution is to edit the file and change its content to:
<pre>
foreman-proxy ALL = NOPASSWD : /usr/bin/puppet cert *, /usr/bin/puppet kick *
Defaults:foreman-proxy !requiretty
</pre>
Might need a service restart, server reboot certainly works.

The config.ru file used for Passenger also changes. Update the @/etc/puppet/rack/config.ru@ file as per the "Puppet release notes":http://docs.puppetlabs.com/puppet/3/reference/release_notes.html#break-puppet-master-rack-configuration-is-changed diff.

h2. How does Foreman work with PuppetDB?

Foreman does not use PuppetDB, nor does PuppetDB use Foreman. While they can both be used at the same time if you wish, there is no integration between these two tools.

In the past Foreman used to use the ActiveRecord based Storeconfigs setup, to access facts but this is now deprecated (see [[Puppet Facts]] for the correct way to configure this now).

Reports can now be stored in PuppetDB (since version 1.1.0) but Foreman uses its own report storage to present reports to you, and will not use the reports stored in PuppetDB.

If you wish to use an alternative to PuppetDB exported resources, you can utilize foreman search API - see "This Blog Entry":http://blog.theforeman.org/2012/01/getting-foreman-search-results-into.html

The "puppetdb_foreman plugin":https://github.com/cernops/puppetdb_foreman can be used to deactivate nodes in PuppetDB automatically when they are deleted from Foreman's database.

h2. I'm not using Storeconfigs, how can I still use Foreman?

See [[Puppet Facts]]

h2. I'm using Storeconfigs, how can I populate various settings in Foreman that are required for hands free (unattended) installations?

See [[Puppet Facts]]

h2. I don't want to use Foreman for unattended installations can I disable it?

see [[Unattended_installations#Deactivation]]

h2. How can I migrate from an other External Node Classifier to Foreman ?

see [[External Nodes#Import-your-external-node-setup-from-an-older-external-node-setup]]

h2. How do I configure my database ?

see [[Database configuration]]

h2. Can I switch from SQLite to MySQL and keep my data ?

see [[Database_configuration]]

h2. How do I start a Rails Console?

Use

cd /usr/share/foreman
rails console

or if you use RHEL6

scl enable ruby193 "rails console"

Warning: Make a backup of your data if you are going to commit any data changes via console.

h2. How do I log my Foreman environments to a different location other than '/var/log'?
<pre>
cd ~foreman/config/environments
vi production.rb
</pre>

Add the following line
<pre>
config.paths["log"] = "/new/log/directory/#{Rails.env}.log"
</pre>

Production.log will now be found and updated at the path specified. Remember to update your logrotations.
Repeat for other environments.

h2. What about other operating systems?

see [[Other_operating_system]]

h2. Will Foreman manage non OpenSource services (e.g. DNS/DHCP etc) ?

Yes! we understand that many enterprises relay on non opensource infrastrucutre as well. We support MS DNS and DHCP services
If you have any additional requirements, please enter a feature request.

h2. Whats planned for the next major release?

See the "roadmap":http://theforeman.org/projects/foreman/roadmap

If you want additional features, please open a new feature request "here":http://theforeman.org/projects/foreman/issues/new !

h2. I want to contribute, how can I do ?

see [[Contribute]]

h2. How do I create resources or use defined types in Foreman?

See [[Instantiate_Puppet_resources]]