Go back

Troubleshooting Issues

This section describes how to troubleshooting common issues in Puppet Foreman Setup.

  1. IP is already used by …error


If you come across above error, goto Interfaces tab, click on Edit button under Action column of displayed interface and remove the public IP from IPv4 Address field, click OK and resubmit.

  1. Host “out of sync” warning

Sometimes if the hosts or puppet server are restarted or if there is some network connectivity issue between hosts and foreman server or puppet version mismatch between the server and agent, you may see out of sync warning for respective host in Foreman console.

For the version mismatch, you can upgrade puppet agent to match the server version and sync host via puppet agent -t

The default time interval for Foreman console for host reporting is 35 minutes. You can decrease that interval by going to “Administer → settings”, search for “puppet_interval” property and update it to shorter interval (eg. 5 minutes) and wait for 5-10 minutes to see if the host is synced. If the hosts are still not synced, you can manually run below command in the host to resolve it-

sudo/opt/puppetlabs/puppet/bin/puppet agent -t

You can also run this same command remotely in Foreman console by following below steps:

  • Goto Hosts → All Hosts and select the check box next to the out of sync host
  • A Select Action button will appear on top right of the hosts table. Select the Schedule Remote Job option from the action list. /img/gcp/puppet-support/select-action-host.png
  • In the displayed form, keep the default values and copy below command in “command” text box, click submit.
  sudo /opt/puppetlabs/puppet/bin/puppet agent -t


  • Once the command executes remotely in the host, it will sync with the server and Foreman should update the host status to sync after few minutes.
Go back