[root@olympic environments]# foreman-rake db:migrate
[root@olympic environments]#

We do not use the API or CLI.

I upgraded to 1.10.1 from 1.9.3 around feb 16

I think the problem was present in at least 1.9.

I'm not sure I see how it could have happened in 1.9, this looks more like a 1.10 only issue. There's a possibility there was some bad data though which has caused the issue on upgrade.

It looks like a problem with a particular smart class parameter or variable associated to the host, which might be difficult to find. What appears to be the problem is that you have a "LookupKey" in the database which should either be a PuppetLookupKey (a smart class parameter) or a VariableLookupKey (a smart variable).

Can you run foreman-rake console and attach the output from running: LookupKey.where(:type => 'LookupKey')

My guess is that some entries in 1.9 had is_param set to NULL rather than true/false and so didn't get migrated properly.

[root@olympic ~]# foreman-rake console
Loading production environment (Rails 3.2.8)
irb(main):001:0> LookupKey.where(:type => 'LookupKey')
LookupKey Load (0.8ms) SELECT "lookup_keys".* FROM "lookup_keys" WHERE "lookup_keys"."type" = 'LookupKey' ORDER BY lookup_keys.key
=> []
irb(main):002:0>

Tanks to your comments I was able to find the bad variables and matchers in the database. They were invisible from the web-interface. Deleting those lines from the database solved my problems. Now I am happy. :-)