Bugzilla update 4.1.3 --> 4.2rc1

[Lauri Lahti]

Hi All,

I tried to to update bugzilla 4.1.3 to 4.2rc1 but update didn't work
so well

Our Bugzilla installation is served by CentOS 4 with Oracle 10.2
database.


When I was executing ./checksetup.pl we got following errors.

Dropping foreign key: bug_tag.tag_id -> tags.id...
Failed SQL: [DROP TRIGGER fk_949096678bffbde6cb5f_uc] Error:
DBD::Oracle::db do failed: ORA-04080: trigger
'FK_949096678BFFBDE6CB5F_UC' does not exist (DBD ERROR:
OCIStmtExecute) [for Statement "DROP TRIGGER
fk_949096678bffbde6cb5f_uc"] at Bugzilla/DB/Oracle.pm line 399
Bugzilla::DB::Oracle::do('undef', 'DROP TRIGGER
fk_949096678bffbde6cb5f_uc') called at Bugzilla/DB.pm line 910
eval {...} called at Bugzilla/DB.pm line 910

Bugzilla::DB::bz_drop_fk('Bugzilla::DB::Oracle=HASH(0xbcde9d0)',
'bug_tag', 'tag_id') called at Bugzilla/DB.pm line 948

Bugzilla::DB::bz_drop_related_fks('Bugzilla::DB::Oracle=HASH(0xbcde9d0)',
'tags', 'id') called at Bugzilla/DB.pm line 1070

Bugzilla::DB::bz_rename_table('Bugzilla::DB::Oracle=HASH(0xbcde9d0)',
'tags', 'tag') called at Bugzilla/Install/DB.pm line 3606
Bugzilla::Install::DB::_rename_tags_to_tag() called at
Bugzilla/Install/DB.pm line 650

Bugzilla::Install::DB::update_table_definitions('HASH(0x99d5588)')
called at ./checksetup.pl line 199
Can't use string ("tags") as a SCALAR ref while "strict refs" in use
at Bugzilla/DB/Schema/Oracle.pm line 389.



When trying to run ./checksetup.pl again I got following errors:


Adding new table tag...
DBD::Oracle::db do failed: ORA-00955: name is already used by an
existing object (DBD ERROR: error possibly near <*> indicator at char
16 in 'CREATE SEQUENCE <*>tag_id_SEQ INCREMENT BY 1 START WITH 1
NOMAXVALUE NOCYCLE NOCACHE') [for Statement "CREATE SEQUENCE
tag_id_SEQ INCREMENT BY 1 START WITH 1 NOMAXVALUE NOCYCLE
NOCACHE"] at Bugzilla/DB/Oracle.pm line 399
Bugzilla::DB::Oracle::do('undef', 'CREATE SEQUENCE tag_id_SEQ
INCREMENT BY 1 START WITH 1 NOM...') called at Bugzilla/DB.pm line
824

Bugzilla::DB::_bz_add_table_raw('Bugzilla::DB::Oracle=HASH(0xb44e8e8)',
'tag', 'HASH(0xb54d1c4)') called at Bugzilla/DB.pm line 783

Bugzilla::DB::bz_add_table('Bugzilla::DB::Oracle=HASH(0xb44e8e8)',
'tag', 'HASH(0xb54d1c4)') called at Bugzilla/DB.pm line 499

Bugzilla::DB::bz_setup_database('Bugzilla::DB::Oracle=HASH(0xb44e8e8)')
called at Bugzilla/DB/Oracle.pm line 636

Bugzilla::DB::Oracle::bz_setup_database('Bugzilla::DB::Oracle=HASH(0xb44e8e8)')
called at ./checksetup.pl line 148



Are there any ways to fix these problems?

Thanks in advance

Br. Lauri Lahti

[Frédéric Buclin]

Le 02. 01. 12 07:29, Lauri Lahti a écrit :

> I tried to to update bugzilla 4.1.3 to 4.2rc1 but update didn't work
> so well

Was 4.1.3 a fresh install, or an upgrade from a previous release? If it
was an upgrade, please indicate from which version.

4.1.3 was in no way considered stable, and you fall in one of the most
painful blockers we had to fix for 4.2rc1.

Give me the information I requested above and I will investigate.
Meanwhile, restore your 4.1.3 backup.


LpSolit

[Lauri Lahti]

Thanks Frederic,

Our installation of Bugzilla 4.1.3 was a fresh install.

I was kind of surprized that installation of 4.2rc1 is actually
working even though installation script failed. I ran DB sanity checks
and there were no problems and all BUGs and related comments and
attachments survived update process.
So far everything have been working normally.

Currently we are testing Bugzilla's suitability for our needs and what
comes to 4.2rc1 it looks like many of Oracle related bugs have been
fixed since 4.1.3 which is very good.

Br. Lauri Lahti

[Lauri Lahti]

On Jan 2, 9:59 pm, Frédéric Buclin <LpSo...@gmail.com> wrote:

I decide to keep using 4.2rc1, because it seems to be working much
better than 4.1.3.
But now i have concern about the risks of doing so?

Obviously install scripts are failing, but the whole installation
seems to be running without any problems.

Will there be some bigger problems when i'm trying to update my
installation to oncoming 4.2 release?

br. Lauri Lahti

[Frédéric Buclin]

Le 06. 01. 12 02:42, Lauri Lahti a écrit :

> I decide to keep using 4.2rc1, because it seems to be working much
> better than 4.1.3.
> But now i have concern about the risks of doing so?

If this is just a test installation, I would recommend to drop the DB
entirely, and recreate a fresh installation using 4.2rc1 directly.
4.2rc1 got many improvements compared to 4.1.3. As there should be no DB
schema changes between 4.2rc1 and 4.2 final, you will have no trouble to
upgrade later.

I will try to reproduce your error this afternoon (I'm downloading and
installing 4.1.3 now).

LpSolit

[Frédéric Buclin]

Le 06. 01. 12 13:22, Frédéric Buclin a écrit :

> I will try to reproduce your error this afternoon (I'm downloading and
> installing 4.1.3 now).

OK, I could reproduce your error when upgrading from 4.1.3 to 4.2rc1,
and I fixed the problem. The fix will be in 4.2 final (or 4.2rc2, if
there is one). Meanwhile, I suggest that you either a) install a fresh
copy of 4.2rc1, or b) you restore your backup from 4.1.3, apply the
patch below to your 4.2rc1 code, and then run checksetup.pl.
checksetup.pl will now work correctly with my patch applied.

You can download the patch from here:

https://bug715870.bugzilla.mozilla.org/attachment.cgi?id=586399

To apply the patch, go into your bugzilla/ root directory (the one for
4.2rc1, not 4.1.3), and execute:

patch -p0 < bug0-8.diff


Thanks for reporting this bug to us before 4.2 final! :)

If you want to see when the patch is committed into the source code,
follow this bug:

https://bugzilla.mozilla.org/show_bug.cgi?id=715870


LpSolit