On Thu, Apr 25, 2013 at 5:24 PM, gen...@allantgroup.com < andyr7777...@gmail.com> wrote:
> > > On Thursday, April 25, 2013 3:19:55 AM UTC-5, ohad wrote: > >> >> >> On Thu, Apr 25, 2013 at 2:00 AM, gen...@allantgroup.com < >> andyr7...@gmail.com> wrote: >> >>> I updated some of my gems, and I think it may be the reason I am getting >>> the following error when the agents try to retrieve a catalog. >>> >>> >>> err: Could not retrieve catalog from remote server: Error 400 on SERVER: >>> The single-table inheritance mechanism failed to locate the subclass: >>> 'Host::Managed'. This error is raised because the column 'type' is reserved >>> for storing the class in case of inheritance. Please rename this column if >>> you didn't intend it to be used for storing the inheritance class or >>> overwrite Puppet::Rails::Host.**inheritance_column to use another >>> column for that information. >>> >> this looks like the development version of foreman, are you using >> it together with storeconfigs? >> >> Ohad >> > > Yes, it is the development version of foreman and yes I am using > storeconfigs. Is there a solution to this, or should I downgrade foreman > to stable? > One of the upcoming changes in 1.2 is to no longer share the db with storeconfigs (as its being replaced in favor of puppetdb anyway)... therefore, if you want to use the latest version and 1.2 at the same time, you would need to dump the db into a new foreman db (or puppet). Ohad > > Thanks, > > Andy > > >> >>> Ruby 1.8.7, I believe apache is using passenger 2.2.11. I tried 3.0.19, >>> but then I get errors in the apache log about not finding files in the >>> /usr/share/puppet/rack/**puppetmasterd/public, which AFAICT are >>> application generated. >>> >>> Everything was working fine before updating the gems. I was updating >>> the gems because I was trying to get foreman working again after updating >>> it. >>> >>> I do not know much about ruby or passenger, so I could use some help >>> figuring out how to fix this issue. At least puppet-dashboard is working, >>> it just isn't getting any new reports due to the problems with puppet. >>> >>> Thanks, >>> >>> Andy >>> >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Puppet Users" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to puppet-users...@**googlegroups.com. >>> To post to this group, send email to puppet...@googlegroups.com. >>> >>> Visit this group at >>> http://groups.google.com/**group/puppet-users?hl=en<http://groups.google.com/group/puppet-users?hl=en> >>> . >>> For more options, visit >>> https://groups.google.com/**groups/opt_out<https://groups.google.com/groups/opt_out> >>> . >>> >>> >>> >> >> -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to puppet-users+unsubscr...@googlegroups.com. > To post to this group, send email to puppet-users@googlegroups.com. > Visit this group at http://groups.google.com/group/puppet-users?hl=en. > For more options, visit https://groups.google.com/groups/opt_out. > > > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
