Login Passwords Fail following upgrade to RT

I initially attempted to upgrade to 4.0.12 and that is when I first
identified the problem. I then went back to 3.8.10 and upgraded each
individual version and tested to see if I could log-out and then back in.
It was when I tried to go from version 3.8.16 to 4.0.0 when I first had
the issue. I intend to go to 4.0.12 one step at a time.

I did run the make upgrade and then /opt/rt4/sbin/rt-setup-database --dba
root --prompt-for-dba-password --action upgrade. It says it will upgrade
3.9.1 through 4.0.0rc7. During this process I get an error after the
Processing 3.9.3 - Now populating database schema message:

[crit]: DBD::mysql::st execute failed: Can’t DROP ‘DelegatedBy’; check
that column/key exists at /opt/rt4/sbin/…/lib/RT/Handle.pm line 503.
(/opt/rt4/sbin/…/lib/RT.pm:340)
DBD::mysql::st execute failed: Can’t DROP ‘DelegatedBy’; check that
column/key exists at /opt/rt4/sbin/…/lib/RT/Handle.pm line 503.

The script stops executing at this point.Date: Tue, 21 May 2013 17:13:59 -0700
From: Thomas Sibley trs@bestpractical.com
To: rt-users@lists.bestpractical.com
Subject: Re: [rt-users] Login Passwords Fail following upgrade to RT
4.0.0
Message-ID: 519C0DC7.70304@bestpractical.com
Content-Type: text/plain; charset=UTF-8

I am currently running RT 3.8.16 and all appears to be working fine. I
have decided to upgrade to RT 4.0.0.

Why 4.0.0 and not 4.0.12? .12 contains two years of bugfixes. There is
no reason to upgrade to something less.

There are a few other differences in the users database between rt3 & rt4.
I have tried to follow the README, UPGRADING & UPGRADING.mysql
directions but cannot find that the new database SCHEMA has changed
during these processes.

Did you run make upgrade-database? It sounds very much like you didn’t
run any database upgrades at all.

Please re-read the README, paying attention to step 6(b) and UPGRADING-4.0:

http://bestpractical.com/rt/docs/latest/README.html
http://bestpractical.com/rt/docs/latest/UPGRADING-4.0.html

Perhaps this will be useful:

Hi,

You got an error and your upgrade failed. Which database do you use and
which version of the DB.

The fact that you don’t have DelegatedBy column suggests that you did
something wrong when was copying RT3’s DB or have DB with column dropped
already.

We had big thread on the list recently with very similar error. Take a look.On Wed, May 22, 2013 at 10:15 PM, dfriend@qcol.net wrote:

I initially attempted to upgrade to 4.0.12 and that is when I first
identified the problem. I then went back to 3.8.10 and upgraded each
individual version and tested to see if I could log-out and then back in.
It was when I tried to go from version 3.8.16 to 4.0.0 when I first had
the issue. I intend to go to 4.0.12 one step at a time.

I did run the make upgrade and then /opt/rt4/sbin/rt-setup-database --dba
root --prompt-for-dba-password --action upgrade. It says it will upgrade
3.9.1 through 4.0.0rc7. During this process I get an error after the
Processing 3.9.3 - Now populating database schema message:

[crit]: DBD::mysql::st execute failed: Can’t DROP ‘DelegatedBy’; check
that column/key exists at /opt/rt4/sbin/…/lib/RT/Handle.pm line 503.
(/opt/rt4/sbin/…/lib/RT.pm:340)
DBD::mysql::st execute failed: Can’t DROP ‘DelegatedBy’; check that
column/key exists at /opt/rt4/sbin/…/lib/RT/Handle.pm line 503.

The script stops executing at this point.

Date: Tue, 21 May 2013 17:13:59 -0700
From: Thomas Sibley trs@bestpractical.com
To: rt-users@lists.bestpractical.com
Subject: Re: [rt-users] Login Passwords Fail following upgrade to RT
4.0.0
Message-ID: 519C0DC7.70304@bestpractical.com
Content-Type: text/plain; charset=UTF-8

On 05/21/2013 06:55 AM, dfriend@qcol.net wrote:

I am currently running RT 3.8.16 and all appears to be working fine. I
have decided to upgrade to RT 4.0.0.

Why 4.0.0 and not 4.0.12? .12 contains two years of bugfixes. There is
no reason to upgrade to something less.

There are a few other differences in the users database between rt3 &
rt4.
I have tried to follow the README, UPGRADING & UPGRADING.mysql
directions but cannot find that the new database SCHEMA has changed
during these processes.

Did you run make upgrade-database? It sounds very much like you didn’t
run any database upgrades at all.

Please re-read the README, paying attention to step 6(b) and UPGRADING-4.0:

README - RT 5.0.3 Documentation - Best Practical
UPGRADING-4.0 - RT 5.0.3 Documentation - Best Practical

Perhaps this will be useful:
Upgrading to RT 4 — Best Practical Solutions


RT Training in Seattle, June 19-20: Training — Best Practical Solutions

Best regards, Ruslan.