Failure report : RT 2.0.60 / Data migration

Hello,

I tested the migration package. I managed to create the dumpfile, but could
not load it into the new database. The process started OK, but then failed
after having created the 885 users with the following message :

Adding 729 to 1786
Adding 12 to 1787
Adding 13 to 1787
[Tue Jan 21 11:22:40 2003] [warning]: Use of uninitialized value in hash
element at ./2to3 line 158.
(/usr/local/rt3/lib/RT.pm:220)
Couldn’t load principal 3 to grant them CommentOnTicket globally
$VAR1 = {
‘PrincipalType’ => ‘Group’,
‘Name’ => ‘CommentOnTicket’,
‘Role’ => ‘Everyone’
};

I am still using MySQL 3.23 as I have some problems migrating to 4 with some
other packages. Can this be the reason?

Blaise

-----Message d’origine-----De : Jesse Vincent [mailto:jesse@bestpractical.com]
Envoyé : lundi 20 janvier 2003 21:20
À : rt-devel@fsck.com
Objet : [rt-devel] RT 2.0.60 / Data migration

RT 2.1.60 now exists. It contains a number of I18N fixes, the requisite
set of bug fixes and and a bunch of enhancements to support…data
migration from RT 2.0. I’m attaching the prototype data migration tools
here. I’d appreciate it if folks would test out data migration, but I
strongly recommend that nobody attempt to migrate a production RT
instance with them yet.

Caveats:

They don't import your Templates. If you've changed them you'll
need to migrate them by hand.

They don't get all Scrips correct just yet.

They're not optimized for large ticket loads.  If you attempt to
import 20,000 tickets with these tools, you're going to be an
unhappy camper.  Once we're reasonably confident that the tools
are importing data correctly, they'll be refactored to handle
large loads more gracefully.

2.0-export > dumpfile # will create a dump of your running RT2 instance

2to3 dumpfile # will turn a virgin rt3 instance into a clone of your RT2
instance.

-j

»|« http://www.bestpractical.com/rt – Trouble Ticketing. Free.

Hello,

I tested the migration package. I managed to create the dumpfile, but could
not load it into the new database. The process started OK, but then failed
after having created the 885 users with the following message :

I am still using MySQL 3.23 as I have some problems migrating to 4 with some
other packages. Can this be the reason?

Blaise

Nah. That’s one of the trickier bits of import code. I’ll try to have a
look later today. While we currently say that we need mysql 4, mysql
3.23 with InnoDB tables should work just fine.

-jesse

»|« http://www.bestpractical.com/rt – Trouble Ticketing. Free.

“JV” == Jesse Vincent jesse@bestpractical.com writes:

JV> Nah. That’s one of the trickier bits of import code. I’ll try to have a
JV> look later today. While we currently say that we need mysql 4, mysql
JV> 3.23 with InnoDB tables should work just fine.

Is the postgresql version ready for testing at any level?

“JV” == Jesse Vincent jesse@bestpractical.com writes:

JV> Nah. That’s one of the trickier bits of import code. I’ll try to have a
JV> look later today. While we currently say that we need mysql 4, mysql
JV> 3.23 with InnoDB tables should work just fine.

Is the postgresql version ready for testing at any level?

I will admit that I last tested postgres at 7.2.1, but yes, it’s worth
testing.

if you ./configure it right, you should be able to type “make
regression” and have RT run through its testsuite.

make regression-quiet will not list all the “ok” tests.

I’ve actually gotten postgres 7.3 mostly running on my dev host, but
hadn’t yet actually had a chance to test RT against it.

»|« http://www.bestpractical.com/rt – Trouble Ticketing. Free.

Attached is a new 2to3 tool. It sucessfully imports the ACL you were
having trouble with. Send me the next error :wink:

»|« http://www.bestpractical.com/rt – Trouble Ticketing. Free.

2to3 (14.1 KB)

OK, you ask for it, you get it :slight_smile:

The import script failed at the same place, but with a slightly different
message.
Looking into the database, it created a few more ACLs than the previous
version, (CommentOnTicket, CreateTicket, ReplyToTicket, ShowTicket,
ModifySelf, OwnTicket, when the previous version only created “superuser”.

Adding 729 to 1786
Adding 12 to 1787
Adding 13 to 1787
[Tue Jan 21 22:04:57 2003] [warning]: Use of uninitialized value in
concatenation (.) or string at ./2to3 line 171.
(/usr/local/rt3/lib/RT.pm:220)
Couldn’t load principal to grant them ShowTicket globally
$VAR1 = {
‘PrincipalType’ => ‘Group’,
‘Name’ => ‘ShowTicket’,
‘Role’ => ‘Owner’
};

Blaise

-----Message d’origine-----De : Jesse Vincent [mailto:jesse@bestpractical.com]
Envoyé : mardi 21 janvier 2003 22:53
À : THAUVIN Blaise (Dir. Informatique FRP)
Cc : rt-devel@fsck.com
Objet : Re: [rt-devel] Failure report : RT 2.0.60 / Data migration

Attached is a new 2to3 tool. It sucessfully imports the ACL you were
having trouble with. Send me the next error :wink:

»|« http://www.bestpractical.com/rt – Trouble Ticketing. Free.

RT 2.1.61 is up, which along with the 2to3 attached to this message
should let you get further. Oh. and the german and french translations
have been updated.On Tue, Jan 21, 2003 at 11:14:35PM +0100, THAUVIN Blaise (Dir. Informatique FRP) wrote:

Couldn’t load principal to grant them ShowTicket globally
$VAR1 = {
‘PrincipalType’ => ‘Group’,
‘Name’ => ‘ShowTicket’,
‘Role’ => ‘Owner’
};

Blaise

»|« http://www.bestpractical.com/rt – Trouble Ticketing. Free.

2to3 (14.5 KB)

It’s getting better, and this time, the problem seems to be with the
specific data in my RT2 database

First I got those warnings :

o 1787
[Wed Jan 22 01:30:01 2003] [warning]: Use of uninitialized value in join or
string at (eval 1419) line 2.
(/usr/local/rt3/lib/RT.pm:220)
[Wed Jan 22 01:30:02 2003] [warning]: Use of uninitialized value in join or
string at (eval 1419) line 2.
(/usr/local/rt3/lib/RT.pm:220)
[Wed Jan 22 01:30:14 2003] [warning]: Use of uninitialized value in join or
string at (eval 1419) line 2.
(/usr/local/rt3/lib/RT.pm:220)
[Wed Jan 22 01:30:15 2003] [warning]: Use of uninitialized value in join or
string at (eval 1419) line 2.
(/usr/local/rt3/lib/RT.pm:220)
Importing ticket 1
transaction 1
attachment 1
transaction 2
transaction 7
attachment 2
attachment 3
attachment 4
transaction 8
transaction 9
attachment 5
attachment 6

Then it crashed with :

       transaction 54

Importing ticket 9
[Wed Jan 22 01:30:37 2003] [debug]: not a recognised queue object.
(/usr/local/rt3/lib/RT/Ticket_Overlay.pm:327)
[Wed Jan 22 01:30:37 2003] [debug]: RT::Ticket=HASH(0x1274b908) No queue
given for ticket creation. (/usr/local/rt3/lib/RT/Ticket_Overlay.pm:332)
[Wed Jan 22 01:30:37 2003] [warning]: Use of uninitialized value in numeric
eq (==) at ./2to3 line 352.
(/usr/local/rt3/lib/RT.pm:220)
Couldn’t create ticket HASH(0xee42d7c) $VAR1 = {
‘Creator’ => ‘220’,
‘LastUpdated’ => ‘2001-09-06 16:07:35’,
‘Due’ => ‘1970-01-01 00:00:00’,
‘Subject’ => ‘test Blaise’,
‘Queue’ => undef,
‘Status’ => ‘resolved’,
‘LastUpdatedBy’ => ‘1484’,
‘EffectiveId’ => ‘9’,
‘Resolved’ => ‘2001-09-06 16:05:35’,
‘Started’ => ‘2001-09-06 16:05:35’,
‘id’ => ‘9’,
’_RecordTransaction’ => 0,
‘Owner’ => ‘1484’,
‘Created’ => ‘2001-09-06 16:04:21’,
‘Requestor’ => [
‘bthauvin@clearchannel.fr’
]
};

If I understand well, there is an old ticket in my database which does not
belong to any queue…

Looking into the original RT2 base, it appears the queue it belongs to is
disabled. I checked in the RT3 database and it has not been imported.

I guess you should export and import disabled objects just in case there are
some dependencies.

Its almost 3am in France, so I guess I’ll try your next version tomorrow
morning…

Blaise

Looking into the original RT2 base, it appears the queue it belongs to is
disabled. I checked in the RT3 database and it has not been imported.

I guess you should export and import disabled objects just in case there are
some dependencies.

I concur. Attached is a new 2.0-export which should export disabled
objects. Thanks very much for being my guinea pig on this one.

Its almost 3am in France, so I guess I’ll try your next version tomorrow
morning…

Hope you had a pleasant night’s sleep.

Blaise

Jesse

»|« http://www.bestpractical.com/rt – Trouble Ticketing. Free.

2.0-export (9.11 KB)