Sure, I'm using this repository deb http://deb.theforeman.org/ precise stable
I upgraded from foreman-postgresql 1.2.3+debian1 foreman 1.2.3+debian1 foreman-proxy 1.2.1+ubuntu1 foreman-installer 1.2.1-debian1 to foreman-postgresql 1.3.0-1 foreman 1.3.0-1 foreman-proxy 1.3.0-1 foreman-installer 1.3.0-1 it looks as if the upgrade didn't make the required changes to the database, or something like that. I dropped the db and recreated it and the error about the missing column went away but still couldn't enroll new nodes. I urgently needed to make this work so I just ripped out foreman. I didn't have time to research the issue further or try to fix foreman. On Wednesday, 16 October 2013 17:24:46 UTC+8, ohad wrote: > > > > > On Wed, Oct 16, 2013 at 11:07 AM, Steve Wray <[email protected]<javascript:> > > wrote: > >> It turned out that there was an update to the foreman package which >> completely broke Puppets ability to enroll new nodes. >> >> Call me old fashioned, I've been a Debian sysadmin for over 10 years, but >> on a 'stable' system an apt-get upgrade is not supposed to break things. >> Thats one of the things Debian is famous for. Just so happens my server is >> running Ubuntu server 'long term support' version and I expected something >> similar there. >> >> > Would you mind sharing information about which version did you upgrade > from <-> to ? > > we take releases very seriously (usually 4 RC with full packages) before > rolling out an upgrade, I'm sorry it didn't work for you this time. > > Ohad > > -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
