Your response is encouraging, thanks. I wasn't using sqlite, I was using postgresql. I have about 100 nodes (and growing) sqlite quickly became unusable.
One of the things I tried was aptitude install with =version but this didn't work, apparently it couldn't find the old versions in the repo. I started downloading the .debs to install the old versions manually but realised it would be quicker to just uninstall foreman, we had just commissioned a bunch of servers, and more arriving all the time, so I really had to just get a move on. Honestly, if it hadn't been a Debian-based system, say CentOS, I'd have been a LOT more cautious about the 8upgrade but I've got so used to things just not breaking in stable (last time anything like that bit me was when someone decided to apply a 'security' patch to sudo). When I have some breathing room I'll do some more tests with the newer version of foreman. On 16 October 2013 20:02, Greg Sutcliffe <greg.sutcli...@gmail.com> wrote: > On 16 October 2013 11:48, Steve Wray <stevedw...@gmail.com> wrote: > >> Sure, I'm using this repository >> >> deb http://deb.theforeman.org/ precise stable >> >> 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. >> > > Firstly, as the deb package maintainer for Foreman, I'm sorry you had > issues. Thanks also for the bug report - we've just tracked down and fixed > an issue which specifically affects sqlite3 upgrades (I'm not sure if you > are on sqlite3, but your symptoms fit, I think). 1.3.0-2 is now in the repo > with the fix. > > With regards to upgrades not breaking things, I agree. We spent some time > discussing the state of the Debian Foreman repo a few weeks ago[1] and one > outcome of that was that we would create a repo for each major version (eg > http://deb.theforeman.org/ precise 1.2) and that 'stable' would track the > latest release. This was done, and as 1.3 was released on Monday, 'stable' > now points to 1.3. The 1.2 repo allows people who wish to be conservative > to lock themselves to a particular release. > > An unavoidable side-effect of this is that since we only had "stable" > before, everyone is currently using it. I accept we could have done a > better job of publicising the existence of the 1.2 repo before 1.3 came out > though. I've just sent a mail to our users and announce lists to make > people more aware of the new repos. > > Once again, apologies for your troubles, and thanks for the feedback. > > Greg > [1]https://groups.google.com/d/msg/foreman-dev/76A7LmuPzLM/O8ob4aEX3VAJ > > -- > You received this message because you are subscribed to a topic in the > Google Groups "Puppet Users" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/puppet-users/Dfgwz8bPYvY/unsubscribe. > To unsubscribe from this group and all its topics, 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. > 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. For more options, visit https://groups.google.com/groups/opt_out.
