Project

General

Profile

FAQ » History » Version 57

« Previous - Version 57/68 (diff) - Next » - Current version
Dominic Cleal, 10/07/2013 10:02 AM
puppetdb_foreman


Common Issues

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='' where login='admin';"

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

Allocate DHCP addresses.

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

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".

Other FAQ

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.

Upgrade puppet from v2 to v3 gotcha

/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:

foreman-proxy ALL = NOPASSWD : /usr/bin/puppet cert *, /usr/bin/puppet kick *
Defaults:foreman-proxy !requiretty

Might need a service restart, server reboot certainly works.

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

The puppetdb_foreman plugin can be used to deactivate nodes in PuppetDB automatically when they are deleted from Foreman's database.

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

See Puppet Facts

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

See Puppet Facts

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

see Unattended_installations

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

see External Nodes

How do I configure my database ?

see Database configuration

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

see Database_configuration

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.

After Foreman 1.3 upgrade reports no longer work

We changed how reports work in the 1.3 release. During 1.3 upgrade, read release notes and update ENC script, otherwise an error will be thrown:

ActionController::RoutingError (No route matches [POST] "/fact_values/create")

What about other operating systems?

see Other_operating_system

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.

Whats planned for the next major release?

See the roadmap

If you want additional features, please open a new feature request here !

I want to contribute, how can I do ?

see Contribute