Foreman-proxy using 100% CPU, not responding, when attempting to update classes/environments

Hi,

When I attempt to refresh the puppet classes/environments, Foreman-proxy
uses all available CPU and does not return.

All I see in the proxy.log is:

I, [2014-08-21T15:33:35.054276 #16466] INFO – : Initializing from Puppet
config file: /etc/puppet/puppet.conf
I, [2014-08-21T15:33:35.128557 #16466] INFO – : Initializing from Puppet
config file: /etc/puppet/puppet.conf
I, [2014-08-21T15:33:35.274510 #16466] INFO – : Initializing from Puppet
config file: /etc/puppet/puppet.conf
I, [2014-08-21T15:33:36.694232 #16466] INFO – : Initializing from Puppet
config file: /etc/puppet/puppet.conf
I, [2014-08-21T15:33:36.757369 #16466] INFO – : Initializing from Puppet
config file: /etc/puppet/puppet.conf
I, [2014-08-21T15:33:36.889878 #16466] INFO – : Initializing from Puppet
config file: /etc/puppet/puppet.conf
I, [2014-08-21T15:33:36.943668 #16466] INFO – : Initializing from Puppet
config file: /etc/puppet/puppet.conf
I, [2014-08-21T15:33:51.224280 #16466] INFO – : Initializing from Puppet
config file: /etc/puppet/puppet.conf
I, [2014-08-21T15:33:51.327197 #16466] INFO – : Initializing from Puppet
config file: /etc/puppet/puppet.conf
I, [2014-08-21T15:33:51.485121 #16466] INFO – : Initializing from Puppet
config file: /etc/puppet/puppet.conf
I, [2014-08-21T15:33:51.564905 #16466] INFO – : Initializing from Puppet
config file: /etc/puppet/puppet.conf
I, [2014-08-21T15:33:58.045986 #16466] INFO – : Initializing from Puppet
config file: /etc/puppet/puppet.conf
I, [2014-08-21T15:34:05.927607 #16466] INFO – : Initializing from Puppet
config file: /etc/puppet/puppet.conf
I, [2014-08-21T15:34:06.157410 #16466] INFO – : Initializing from Puppet
config file: /etc/puppet/puppet.conf
I, [2014-08-21T15:34:06.236268 #16466] INFO – : Initializing from Puppet
config file: /etc/puppet/puppet.conf
I, [2014-08-21T15:34:06.393136 #16466] INFO – : Initializing from Puppet
config file: /etc/puppet/puppet.conf
I, [2014-08-21T15:34:48.686371 #16466] INFO – : Initializing from Puppet
config file: /etc/puppet/puppet.conf
I, [2014-08-21T15:34:48.846028 #16466] INFO – : Initializing from Puppet
config file: /etc/puppet/puppet.conf
I, [2014-08-21T15:34:49.222526 #16466] INFO – : Initializing from Puppet
config file: /etc/puppet/puppet.conf
I, [2014-08-21T15:34:49.431189 #16466] INFO – : Initializing from Puppet
config file: /etc/puppet/puppet.conf
I, [2014-08-21T15:34:51.959573 #16466] INFO – : Initializing from Puppet
config file: /etc/puppet/puppet.conf
I, [2014-08-21T15:34:52.106170 #16466] INFO – : Initializing from Puppet
config file: /etc/puppet/puppet.conf
I, [2014-08-21T15:34:52.382839 #16466] INFO – : Initializing from Puppet
config file: /etc/puppet/puppet.conf
I, [2014-08-21T15:34:52.513622 #16466] INFO – : Initializing from Puppet
config file: /etc/puppet/puppet.conf
I, [2014-08-21T15:34:55.380094 #16466] INFO – : Initializing from Puppet
config file: /etc/puppet/puppet.conf
I, [2014-08-21T15:34:55.595646 #16466] INFO – : Initializing from Puppet
config file: /etc/puppet/puppet.conf
I, [2014-08-21T15:34:55.949059 #16466] INFO – : Initializing from Puppet
config file: /etc/puppet/puppet.conf
I, [2014-08-21T15:34:56.239551 #16466] INFO – : Initializing from Puppet
config file: /etc/puppet/puppet.conf
I, [2014-08-21T15:35:04.168060 #16466] INFO – : Initializing from Puppet
config file: /etc/puppet/puppet.conf
I, [2014-08-21T15:35:04.422434 #16466] INFO – : Initializing from Puppet
config file: /etc/puppet/puppet.conf
I, [2014-08-21T15:35:04.562512 #16466] INFO – : Initializing from Puppet
config file: /etc/puppet/puppet.conf
I, [2014-08-21T15:35:04.660988 #16466] INFO – : Initializing from Puppet
config file: /etc/puppet/puppet.conf

I upgraded from Foreman 1.5.0 to 1.5.2 yesterday, and importing
classes/environments were working yesterday.

This appears to have started after adding a new environment to puppet.conf:

> [myenc]
> modulepath =
> /etc/puppet/environments/myenc/modules:/etc/puppet/environments/common/modules
> config_version =

I tried removing that section from the config, but that doesn't appear to
change anything.

The log messages don't give me much to go on, so I'm not sure what else to
look at.

-Doug