Upgrading in stages did solve the problem. I downloaded version 3.9.7 which is the version Lifecycle was introduced. Upgrading using this version and then upgrading using the latest version of the code completed without errors. From the log I believe I am now on 4.2.10.
I'll back up and restore the unupgraded database to reproduce the complete error message. ~Joshua On Fri, Feb 6, 2015 at 2:02 PM, Alex Vandiver <ale...@bestpractical.com> wrote: > On Fri, 6 Feb 2015 13:44:06 -0500 Joshua Lansford < > joshua.lansf...@laserlinc.com> wrote: > > Ok. So I have done some additional investigation and here is what I have > > found. The new Queues table has two new fields named Lifecycle and > > SubjectTag. Lifecycle field is accessed in the RT::Init which is called > at > > the top of action_insert before it can do the insert portion of the first > > upgrade step... I think. It is looking like the code is assuming stuff > > about the database structure which isn't true just in trying to set up to > > do the upgrade steps. > > Please show the complete output of 'make upgrade-database', not just a > small snippet. > > > I suppose this means I am trying to jump too many versions at once and I > > need to do an intermediate upgrade at an intermediate step. Probably at > > the version which introduces these columns. If that version couldn't > have > > upgraded everyone would have gotten stuck. > > It shouldn't be necessary to to the upgrade in multiple steps. > - Alex >