[Rtir] Upgrade from RT 3.8.10 / RTIR 2.6.1 to RT 4.05 and RTIR 3.0.0 RC1 Part I / was Re: RT 4.x status

[Marco Thorbruegge]

Hello again,

this time it went better. :-)

This is what i did:

- import a recent dump of the RT3 database as RT4 (so there are
basically two copies of the same database, one is named rt3, the other
one is named rt4).

- did some adjustments to /opt/rt4/etc/RT_Siteconfig.pm:

Set($DatabaseType, 'mysql');
Set($DatabaseUser, '<USER>');
Set($DatabasePassword, '<PASSWORD>');
Set($DatabaseName, 'rt4');

(Use here the name of the database you want to convert, in my case rt4,
which is a 1:1 copy of rt3. The rt3 database will not be touched)

- sudo make upgrade-database

(went through smoothly)

- sudo <PATH-TO-SOURCES>/etc/upgrade/upgrade-articles

(for conversion of the RTFM articles). Worked fine.

For testing i started the standalone server; i could login with my
credentials from RT3 (as expected), and see all my tickets. I stopped
the standalone server.

Now i installed RTIR 3.0.0 RC1, by:

perl Makefile.PL
sudo make install

and added the @plugin part in RT_Siteconfig.

This went also well, and i have a working instance of RTIR 3.0.0,
upgraded from RTIR 2.6.1.


Now starting the standalone server, and i can login and again see all my
tickets, etc.

I ran into some problems; i will list them in the following email.

Cheers,
Marco







On 14/03/12 08:54, Marco Thorbruegge wrote:
> Hi,
> 
> thanks for the quick answer!
> 
>> This implies that you ran the upgrade twice, or are running it against
>> a 4.0 schema.  ACL.DelegatedBy exists in 3.8 and is removed in
>> etc/upgrade/3.9.3  etc/upgrade/3.9.2 relies on it being there to clean
>> out old data.
>>
>> You should check the schema of the ACL table before you start your
>> upgrade (with a clean import of 3.8.10, be sure that EVERY table in
>> your rt4 database is gone before you import 3.8.10's data).
> 
> I'll re-do it from scratch, and regard your hint. I'll report afterwards.
> 
> Regards,
> Marco