6.7. Omni-Environment Already Exists Error

This FAQ covers what to do when running simp config outputs an "Unable to configure: Invalid SIMP omni-environment for 'production' exists" error

If installing SIMP on a system that has a pre-existing production Puppet Environment, you may encounter the following error when running simp config:

Unable to configure: Invalid SIMP omni-environment for 'production' exists:
  >> Puppet environment 'production' exists
  >> Secondary environment 'production' does not exist

or (depending on the version):

Unabled to configure: Invalid SIMP omni-environment for 'production' exists:
  >> Puppet environment 'production' exists
  >> Secondary environment 'production' does not exist

6.7.1. Resolution Options

6.7.1.1. A New Start

If you want to start clean, then just rename the production/ directory (/var/simp/environments/production) to production.bak and re-run simp config and simp bootstrap.

6.7.1.2. A Different Environment

If you want to keep your existing production environment, you can use an alternate environment during your initial configuration of the system.

To do this, see HOWTO Use an Alternate ‘simp config’ Environment.

Remember to assign nodes to this environment using your ENC of choice.

For a simple built-in solution, see HOWTO Set Up SIMP’s External Node Classifier.

6.7.2. Puppet Enterprise Users

If you are using Puppet Enterprise, we recommend you use a control repo. See the section on HOWTO Set up a SIMP Environment in a Control Repository.