upgrade bugzilla and migrate database from 2.16.3 to 2.20

Hi group,

i tried to migrate our bugzilla installation (suse linux) from version 
2.16.3 to 2.20. I used the CVS upgrade and it seemed to work perfect. The 
check checksetup.pl script dedected errors in the database (mysql). Droping 
the database and running the checksetup spript worked fine,  but I want to 
migrate the existing database to version 2.20. I did not find any HOWTO.
Can anybody help?

regards Thomas Mayer 


0
Thomas
1/30/2006 11:10:43 AM
mozilla.support.bugzilla 10158 articles. 0 followers. Post Follow

6 Replies
723 Views

Similar Articles

[PageSpeed] 44

Thomas Mayer wrote:
> i tried to migrate our bugzilla installation (suse linux) from version 
> 2.16.3 to 2.20. I used the CVS upgrade and it seemed to work perfect. The 
> check checksetup.pl script dedected errors in the database (mysql). Droping 
> the database and running the checksetup spript worked fine,  but I want to 
> migrate the existing database to version 2.20. I did not find any HOWTO.
> Can anybody help?

checksetup.pl should do this. If it's not working, you need to post the
errors here.

Gerv
0
Gervase
2/10/2006 9:19:55 AM
Did you grant your Bugzilla user access to the DB?

---
Kevin Benton
Perl/Bugzilla Developer/Administrator, Perforce SCM Administrator
Personal Computing Systems Group
Advanced Micro Devices
=20
The opinions stated in this communication do not necessarily reflect the
view of Advanced Micro Devices and have not been reviewed by management.
This communication may contain sensitive and/or confidential and/or
proprietary information.  Distribution of such information is strictly
prohibited without prior consent of Advanced Micro Devices.  This
communication is for the intended recipient(s) only.  If you have
received this communication in error, please notify the sender, then
destroy any remaining copies of this communication.

> -----Original Message-----
> From: support-bugzilla-bounces@lists.mozilla.org
[mailto:support-bugzilla-
> bounces@lists.mozilla.org] On Behalf Of Brian Tucker
> Sent: Friday, February 17, 2006 9:01 AM
> To: support-bugzilla@lists.mozilla.org
> Subject: RE:upgrade bugzilla and migrate database from 2.16.3 to 2.20
>=20
> We are trying to do the same thing.
>=20
> I tried this from another post:
> have migrated my *Bugzilla **2.16* to *Bugzilla* 2.19.2 as follow:
> - on the *2.16* -> % mysqldump -u root -p --opt --all bugs > bugs.sql
> - copy the bugs.sql to the new server (2.18)
> - rename bugs on the new server (2.18)
> - % mysqladmin create bugs
> - % mysql bugs < bugs.sql
> - % mysqladmin flush-privileges
> - % ./checksetup.pl
> - % ./collectstats.pl
>=20
> bug the checksetup.pl script errored out and gives me this message
>=20
> DBD::mysql::st execute failed: Unknown column 'groups.id' in 'field
> list' [for Statement "SELECT groups.id, products.id, groups.name,
> products.name FROM groups, products WHERE isbuggroup !=3D 0"] at
> ./checksetup.pl line 3317
>=20
>=20
>=20
>=20
>=20
> _______________________________________________
> support-bugzilla mailing list
> support-bugzilla@lists.mozilla.org
> https://lists.mozilla.org/listinfo/support-bugzilla


0
Benton
2/17/2006 6:24:55 PM
> >>> We are trying to do the same thing.
> >>>
> >>> I tried this from another post:
> >>> have migrated my *Bugzilla **2.16* to *Bugzilla* 2.19.2 as follow:
> >>> - on the *2.16* -> % mysqldump -u root -p --opt --all bugs >
bugs.sql
> >>> - copy the bugs.sql to the new server (2.18)
> >>> - rename bugs on the new server (2.18)
> >>> - % mysqladmin create bugs
> >>> - % mysql bugs < bugs.sql
> >>> - % mysqladmin flush-privileges
> >>> - % ./checksetup.pl
> >>> - % ./collectstats.pl
> >>>
> >>> bug the checksetup.pl script errored out and gives me this message
> >>>
> >>> DBD::mysql::st execute failed: Unknown column 'groups.id' in
'field
> >>> list' [for Statement "SELECT groups.id, products.id, groups.name,
> >>> products.name FROM groups, products WHERE isbuggroup !=3D 0"] at
> >>> ./checksetup.pl line 3317
> >>>
> >>>
> >>>
> >>>
> >>>
> >>> _______________________________________________
> >>> support-bugzilla mailing list
> >>> support-bugzilla@lists.mozilla.org
> >>> https://lists.mozilla.org/listinfo/support-bugzilla
> >>>
> >>
> >>
> >>
> >> _______________________________________________
> >> support-bugzilla mailing list
> >> support-bugzilla@lists.mozilla.org
> >> https://lists.mozilla.org/listinfo/support-bugzilla
> >>
> >>
> >>
> >>
> >>
> > I was doing it as root for the purpose of testing... Maybe this is a
> > stupid question but if its root do I still have to specifically
grant
> > it access to the database? How would I do that if I needed to?
> >
> > _______________________________________________
> > support-bugzilla mailing list
> > support-bugzilla@lists.mozilla.org
> > https://lists.mozilla.org/listinfo/support-bugzilla
> >
> >
> >
> I tried :
> mysql -u root -p
>  >grant all on bugs to root;
>  >quit;
> $./checksetup.pl
>=20
> and it gave me the same error:
>=20
> DBD::mysql::st execute failed: Unknown column 'groups.id' in 'field
> list' [for Statement "SELECT groups.id, products.id, groups.name,
> products.name FROM groups, products WHERE isbuggroup !=3D 0"] at
> ./checksetup.pl line 3317
>=20
> There are a lot of legacy bugs from another peice of software in it
that
> could be adding complications to this situation.
> I also did : mysql -u root -p
>  >select * from bugs;
>  >quit;
>=20
> To make sure the bugs are indeed there and they are. So there is
> something messed up that is keeping the ./checksetup from working the
> way it is supposed to. Do you have any other suggestions?

You're trying to make Bugzilla use MySQL as the root user?  That's not a
good thing.  You're going to want to create a user (bugs or something
like it) with a password.  It might look something like this:

grant all privileges on bugs.* to 'bugs'@'localhost' identified by
'my_bugs_user_password';

Once you've done that, you will need to update your 'localconfig' file
appropriately (checking $db_user, $db_pass, ..., then re-run
checksetup.pl.  If that fails, send us the output of checksetup.pl.

---
Kevin Benton
Perl/Bugzilla Developer/Administrator, Perforce SCM Administrator
Personal Computing Systems Group
Advanced Micro Devices
=20
The opinions stated in this communication do not necessarily reflect the
view of Advanced Micro Devices and have not been reviewed by management.
This communication may contain sensitive and/or confidential and/or
proprietary information.  Distribution of such information is strictly
prohibited without prior consent of Advanced Micro Devices.  This
communication is for the intended recipient(s) only.  If you have
received this communication in error, please notify the sender, then
destroy any remaining copies of this communication.

0
Benton
2/17/2006 8:12:13 PM
> -----Original Message-----
> From: Brian Tucker [mailto:btucker@asinc.com]
> Sent: Monday, February 20, 2006 7:02 AM
> To: Benton, Kevin
> Cc: support-bugzilla@lists.mozilla.org
> Subject: Re: upgrade bugzilla and migrate database from 2.16.3 to 2.20
>=20
> Benton, Kevin wrote:
>=20
> >>>>>We are trying to do the same thing.
> >>>>>
> >>>>>I tried this from another post:
> >>>>>have migrated my *Bugzilla **2.16* to *Bugzilla* 2.19.2 as
follow:
> >>>>>- on the *2.16* -> % mysqldump -u root -p --opt --all bugs >
> >>>>>
> >>>>>
> >bugs.sql
> >
> >
> >>>>>- copy the bugs.sql to the new server (2.18)
> >>>>>- rename bugs on the new server (2.18)
> >>>>>- % mysqladmin create bugs
> >>>>>- % mysql bugs < bugs.sql
> >>>>>- % mysqladmin flush-privileges
> >>>>>- % ./checksetup.pl
> >>>>>- % ./collectstats.pl
> >>>>>
> >>>>>bug the checksetup.pl script errored out and gives me this
message
> >>>>>
> >>>>>DBD::mysql::st execute failed: Unknown column 'groups.id' in
> >>>>>
> >>>>>
> >'field
> >
> >
> >>>>>list' [for Statement "SELECT groups.id, products.id, groups.name,
> >>>>>products.name FROM groups, products WHERE isbuggroup !=3D 0"] at
> >>>>>./checksetup.pl line 3317
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>_______________________________________________
> >>>>>support-bugzilla mailing list
> >>>>>support-bugzilla@lists.mozilla.org
> >>>>>https://lists.mozilla.org/listinfo/support-bugzilla
> >>>>>
> >>>>>
> >>>>>
> >>>>
> >>>>_______________________________________________
> >>>>support-bugzilla mailing list
> >>>>support-bugzilla@lists.mozilla.org
> >>>>https://lists.mozilla.org/listinfo/support-bugzilla
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>I was doing it as root for the purpose of testing... Maybe this is
a
> >>>stupid question but if its root do I still have to specifically
> >>>
> >>>
> >grant
> >
> >
> >>>it access to the database? How would I do that if I needed to?
> >>>
> >>>_______________________________________________
> >>>support-bugzilla mailing list
> >>>support-bugzilla@lists.mozilla.org
> >>>https://lists.mozilla.org/listinfo/support-bugzilla
> >>>
> >>>
> >>>
> >>>
> >>>
> >>I tried :
> >>mysql -u root -p
> >> >grant all on bugs to root;
> >> >quit;
> >>$./checksetup.pl
> >>
> >>and it gave me the same error:
> >>
> >>DBD::mysql::st execute failed: Unknown column 'groups.id' in 'field
> >>list' [for Statement "SELECT groups.id, products.id, groups.name,
> >>products.name FROM groups, products WHERE isbuggroup !=3D 0"] at
> >>./checksetup.pl line 3317
> >>
> >>There are a lot of legacy bugs from another peice of software in it
> >>
> >>
> >that
> >
> >
> >>could be adding complications to this situation.
> >>I also did : mysql -u root -p
> >> >select * from bugs;
> >> >quit;
> >>
> >>To make sure the bugs are indeed there and they are. So there is
> >>something messed up that is keeping the ./checksetup from working
the
> >>way it is supposed to. Do you have any other suggestions?
> >>
> >>
> >
> >You're trying to make Bugzilla use MySQL as the root user?  That's
not a
> >good thing.  You're going to want to create a user (bugs or something
> >like it) with a password.  It might look something like this:
> >
> >grant all privileges on bugs.* to 'bugs'@'localhost' identified by
> >'my_bugs_user_password';
> >
> >Once you've done that, you will need to update your 'localconfig'
file
> >appropriately (checking $db_user, $db_pass, ..., then re-run
> >checksetup.pl.  If that fails, send us the output of checksetup.pl.
> >
> >---
> >Kevin Benton
> >Perl/Bugzilla Developer/Administrator, Perforce SCM Administrator
> >Personal Computing Systems Group
> >Advanced Micro Devices
> >
> >The opinions stated in this communication do not necessarily reflect
the
> >view of Advanced Micro Devices and have not been reviewed by
management.
> >This communication may contain sensitive and/or confidential and/or
> >proprietary information.  Distribution of such information is
strictly
> >prohibited without prior consent of Advanced Micro Devices.  This
> >communication is for the intended recipient(s) only.  If you have
> >received this communication in error, please notify the sender, then
> >destroy any remaining copies of this communication.
> >
> >_______________________________________________
> >support-bugzilla mailing list
> >support-bugzilla@lists.mozilla.org
> >https://lists.mozilla.org/listinfo/support-bugzilla
> >
> >
> >
> >
> >
> As I said before I was using root to test. I have however setup an
> additional user that has permissions to this database now. After
running
> checksetup again I have encountered the same problem that I posted
> before. In hopes you might have some additional advice I am posting
the
> full screen dump for you to look at.  It is as follows:
>=20
> Checking perl modules ...
> Checking for       AppConfig (v1.52)   ok: found v1.56
> Checking for             CGI (v2.93)   ok: found v3.10
> Checking for    Data::Dumper (any)     ok: found v2.121_02
> Checking for    Date::Format (v2.21)   ok: found v2.22
> Checking for             DBI (v1.38)   ok: found v1.48
> Checking for      File::Spec (v0.84)   ok: found v3.01
> Checking for      File::Temp (any)     ok: found v0.14
> Checking for        Template (v2.08)   ok: found v2.14
> Checking for      Text::Wrap (v2001.0131) ok: found v2005.0824
> Checking for    Mail::Mailer (v1.65)   ok: found v1.73
> Checking for        Storable (any)     ok: found v2.13
>=20
> The following Perl modules are optional:
> Checking for              GD (v1.20)    not found
> Checking for     Chart::Base (v1.0)     not found
> Checking for     XML::Parser (any)     ok: found v2.34
> Checking for       GD::Graph (any)      not found
> Checking for GD::Text::Align (any)      not found
> Checking for     PatchReader (v0.9.4)   not found
>=20
> If you you want to see graphical bug charts (plotting historical data
over
> time), you should install libgd and the following Perl modules:
>=20
> GD:          /usr/bin/perl -MCPAN -e 'install "GD"'
> Chart:       /usr/bin/perl -MCPAN -e 'install "Chart::Base"'
>=20
> If you you want to see graphical bug reports (bar, pie and line charts
of
> current data), you should install libgd and the following Perl
modules:
>=20
> GD:              /usr/bin/perl -MCPAN -e 'install "GD"'
> GD::Graph:       /usr/bin/perl -MCPAN -e 'install "GD::Graph"'
> GD::Text::Align: /usr/bin/perl -MCPAN -e 'install "GD::Text::Align"'
>=20
> If you want to see pretty HTML views of patches, you should install
the
> PatchReader module:
> PatchReader: /usr/bin/perl -MCPAN -e 'install "PatchReader"'
> Checking user setup ...
> Removing existing compiled templates ...
> Precompiling templates ...
> Checking for      DBD::mysql (v2.9003) ok: found v2.9007
> Checking for           MySQL (v3.23.41) ok: found v4.1.16
>=20
> DBD::mysql::st execute failed: Unknown column 'groups.id' in 'field
> list' [for Statement "SELECT groups.id, products.id, groups.name,
> products.name FROM groups, products WHERE isbuggroup !=3D 0"] at
> ./checksetup.pl line 3317
>=20
>=20

What's the output of "describe groups" if you do it from the MySQL
prompt (connected to your bugs DB)?  This would be a good time to grab a
backup and store it from prior to your upgrade.  As a near-last-resort,
you might want to consider upgrading to 2.18 first, then 2.20 just to
see if it makes a difference.

---
Kevin Benton
Perl/Bugzilla Developer/Administrator, Perforce SCM Administrator
Personal Computing Systems Group
Advanced Micro Devices
=20
The opinions stated in this communication do not necessarily reflect the
view of Advanced Micro Devices and have not been reviewed by management.
This communication may contain sensitive and/or confidential and/or
proprietary information.  Distribution of such information is strictly
prohibited without prior consent of Advanced Micro Devices.  This
communication is for the intended recipient(s) only.  If you have
received this communication in error, please notify the sender, then
destroy any remaining copies of this communication.

0
Benton
2/20/2006 4:45:47 PM
> >>>>>>>We are trying to do the same thing.
> >>>>>>>
> >>>>>>>I tried this from another post:
> >>>>>>>have migrated my *Bugzilla **2.16* to *Bugzilla* 2.19.2 as
> >>>>>>>
> >>>>>>>
> >follow:
> >
> >
> >>>>>>>- on the *2.16* -> % mysqldump -u root -p --opt --all bugs >
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>bugs.sql
> >>>
> >>>
> >>>
> >>>
> >>>>>>>- copy the bugs.sql to the new server (2.18)
> >>>>>>>- rename bugs on the new server (2.18)
> >>>>>>>- % mysqladmin create bugs
> >>>>>>>- % mysql bugs < bugs.sql
> >>>>>>>- % mysqladmin flush-privileges
> >>>>>>>- % ./checksetup.pl
> >>>>>>>- % ./collectstats.pl
> >>>>>>>
> >>>>>>>bug the checksetup.pl script errored out and gives me this
> >>>>>>>
> >>>>>>>
> >message
> >
> >
> >>>>>>>DBD::mysql::st execute failed: Unknown column 'groups.id' in
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>'field
> >>>
> >>>
> >>>
> >>>
> >>>>>>>list' [for Statement "SELECT groups.id, products.id,
groups.name,
> >>>>>>>products.name FROM groups, products WHERE isbuggroup !=3D 0"] =
at
> >>>>>>>./checksetup.pl line 3317
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>>_______________________________________________
> >>>>>>>support-bugzilla mailing list
> >>>>>>>support-bugzilla@lists.mozilla.org
> >>>>>>>https://lists.mozilla.org/listinfo/support-bugzilla
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>_______________________________________________
> >>>>>>support-bugzilla mailing list
> >>>>>>support-bugzilla@lists.mozilla.org
> >>>>>>https://lists.mozilla.org/listinfo/support-bugzilla
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>I was doing it as root for the purpose of testing... Maybe this
is
> >>>>>
> >>>>>
> >a
> >
> >
> >>>>>stupid question but if its root do I still have to specifically
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>grant
> >>>
> >>>
> >>>
> >>>
> >>>>>it access to the database? How would I do that if I needed to?
> >>>>>
> >>>>>_______________________________________________
> >>>>>support-bugzilla mailing list
> >>>>>support-bugzilla@lists.mozilla.org
> >>>>>https://lists.mozilla.org/listinfo/support-bugzilla
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>I tried :
> >>>>mysql -u root -p
> >>>>
> >>>>
> >>>>>grant all on bugs to root;
> >>>>>quit;
> >>>>>
> >>>>>
> >>>>$./checksetup.pl
> >>>>
> >>>>and it gave me the same error:
> >>>>
> >>>>DBD::mysql::st execute failed: Unknown column 'groups.id' in
'field
> >>>>list' [for Statement "SELECT groups.id, products.id, groups.name,
> >>>>products.name FROM groups, products WHERE isbuggroup !=3D 0"] at
> >>>>./checksetup.pl line 3317
> >>>>
> >>>>There are a lot of legacy bugs from another peice of software in
it
> >>>>
> >>>>
> >>>>
> >>>>
> >>>that
> >>>
> >>>
> >>>
> >>>
> >>>>could be adding complications to this situation.
> >>>>I also did : mysql -u root -p
> >>>>
> >>>>
> >>>>>select * from bugs;
> >>>>>quit;
> >>>>>
> >>>>>
> >>>>To make sure the bugs are indeed there and they are. So there is
> >>>>something messed up that is keeping the ./checksetup from working
> >>>>
> >>>>
> >the
> >
> >
> >>>>way it is supposed to. Do you have any other suggestions?
> >>>>
> >>>>
> >>>>
> >>>>
> >>>You're trying to make Bugzilla use MySQL as the root user?  That's
> >>>
> >>>
> >not a
> >
> >
> >>>good thing.  You're going to want to create a user (bugs or
something
> >>>like it) with a password.  It might look something like this:
> >>>
> >>>grant all privileges on bugs.* to 'bugs'@'localhost' identified by
> >>>'my_bugs_user_password';
> >>>
> >>>Once you've done that, you will need to update your 'localconfig'
> >>>
> >>>
> >file
> >
> >
> >>>appropriately (checking $db_user, $db_pass, ..., then re-run
> >>>checksetup.pl.  If that fails, send us the output of checksetup.pl.
> >>>
> >>As I said before I was using root to test. I have however setup an
> >>additional user that has permissions to this database now. After
> >>
> >>
> >running
> >
> >
> >>checksetup again I have encountered the same problem that I posted
> >>before. In hopes you might have some additional advice I am posting
> >>
> >>
> >the
> >
> >
> >>full screen dump for you to look at.  It is as follows:
> >>
> >>Checking perl modules ...
> >>Checking for       AppConfig (v1.52)   ok: found v1.56
> >>Checking for             CGI (v2.93)   ok: found v3.10
> >>Checking for    Data::Dumper (any)     ok: found v2.121_02
> >>Checking for    Date::Format (v2.21)   ok: found v2.22
> >>Checking for             DBI (v1.38)   ok: found v1.48
> >>Checking for      File::Spec (v0.84)   ok: found v3.01
> >>Checking for      File::Temp (any)     ok: found v0.14
> >>Checking for        Template (v2.08)   ok: found v2.14
> >>Checking for      Text::Wrap (v2001.0131) ok: found v2005.0824
> >>Checking for    Mail::Mailer (v1.65)   ok: found v1.73
> >>Checking for        Storable (any)     ok: found v2.13
> >>
> >>The following Perl modules are optional:
> >>Checking for              GD (v1.20)    not found
> >>Checking for     Chart::Base (v1.0)     not found
> >>Checking for     XML::Parser (any)     ok: found v2.34
> >>Checking for       GD::Graph (any)      not found
> >>Checking for GD::Text::Align (any)      not found
> >>Checking for     PatchReader (v0.9.4)   not found
> >>
> >>If you you want to see graphical bug charts (plotting historical
data
> >>
> >>
> >over
> >
> >
> >>time), you should install libgd and the following Perl modules:
> >>
> >>GD:          /usr/bin/perl -MCPAN -e 'install "GD"'
> >>Chart:       /usr/bin/perl -MCPAN -e 'install "Chart::Base"'
> >>
> >>If you you want to see graphical bug reports (bar, pie and line
charts
> >>
> >>
> >of
> >
> >
> >>current data), you should install libgd and the following Perl
> >>
> >>
> >modules:
> >
> >
> >>GD:              /usr/bin/perl -MCPAN -e 'install "GD"'
> >>GD::Graph:       /usr/bin/perl -MCPAN -e 'install "GD::Graph"'
> >>GD::Text::Align: /usr/bin/perl -MCPAN -e 'install "GD::Text::Align"'
> >>
> >>If you want to see pretty HTML views of patches, you should install
> >>
> >>
> >the
> >
> >
> >>PatchReader module:
> >>PatchReader: /usr/bin/perl -MCPAN -e 'install "PatchReader"'
> >>Checking user setup ...
> >>Removing existing compiled templates ...
> >>Precompiling templates ...
> >>Checking for      DBD::mysql (v2.9003) ok: found v2.9007
> >>Checking for           MySQL (v3.23.41) ok: found v4.1.16
> >>
> >>DBD::mysql::st execute failed: Unknown column 'groups.id' in 'field
> >>list' [for Statement "SELECT groups.id, products.id, groups.name,
> >>products.name FROM groups, products WHERE isbuggroup !=3D 0"] at
> >>./checksetup.pl line 3317
> >>
> >>
> >>
> >>
> >
> >What's the output of "describe groups" if you do it from the MySQL
> >prompt (connected to your bugs DB)?  This would be a good time to
grab a
> >backup and store it from prior to your upgrade.  As a
near-last-resort,
> >you might want to consider upgrading to 2.18 first, then 2.20 just to
> >see if it makes a difference.
>
> Describe groups yields this :
>=20
> mysql> describe groups;
> +-------------+--------------+------+-----+---------+-------+
> | Field           | Type         | Null | Key | Default | Extra |
> +-------------+--------------+------+-----+---------+-------+
> | bit              | bigint(20)   |           | PRI | 0       |
|
> | name          | varchar(255) |        | UNI |         |       |
> | description  | text           |      |     |         |       |
> | isbuggroup  | tinyint(4)   |      |      | 0       |       |
> | userregexp  | tinytext       |      |     |         |       |
> | isactive        | tinyint(4)   |      |     | 1       |       |
> +-------------+--------------+------+-----+---------+-------+
> 6 rows in set (0.00 sec)
>=20
>=20
> This install is actually a port from another box. What I have done or
> attempted to do is copy an existing 2.16 database to another 2.16
> databse on a new machine and then upgrade to 2.2. I have also tried
> creating a fresh blank 2.2 database and importing the data from the
2.16
> database on the original machine. Both of these methods yield problems
> when I run checksetup.pl  The data seems to be importing correctly at
> least for the most part ( it does not spit out errors during the
process
> ) However, checksetup fails and you can not get access to any of the
> pages except the main page and the login page. If you try to run a
query
> from teh web side in 2.2 it gives you a software error.
>=20
> If using the 2.16 database and the 2.16 page you run a query you get
> results and it works. The only problem there is checksetup fails when
it
> tries to create a table that already exists and it will not let you
log
> into the system to edit anything b/c the format is diff. On our 2.16
> install that was done before I got here somebody tweaked the login to
be
> in the form of userid and password instead of the 2.16 method of
> userid@email.com  and password. So of course if I try to login as
myself
> it says Sorry that doesnt meet the email criteria, but if you put in
the
> email it says no user by that name. Now I could go in and manually add
> an email to all users to see if that works and tweak it from there.
That
> still however leaves the problem of checksetup failing.
>=20
>=20

>From what I see below, your groups table is corrupt.  It may not be
worth the risk to trust your current Bugzilla database (at least the one
described below).  You might want to go back to a known-good backup and
restore from it.  Note the first field listed is "bit" rather than "id".

---
Kevin Benton
Perl/Bugzilla Developer/Administrator, Perforce SCM Administrator
Personal Computing Systems Group
Advanced Micro Devices
=20
The opinions stated in this communication do not necessarily reflect the
view of Advanced Micro Devices and have not been reviewed by management.
This communication may contain sensitive and/or confidential and/or
proprietary information.  Distribution of such information is strictly
prohibited without prior consent of Advanced Micro Devices.  This
communication is for the intended recipient(s) only.  If you have
received this communication in error, please notify the sender, then
destroy any remaining copies of this communication.

0
Benton
2/20/2006 5:58:51 PM
> mysql> describe milestones;
> +------------+-------------+------+-----+---------+-------+
> | Field      | Type        | Null | Key | Default | Extra |
> +------------+-------------+------+-----+---------+-------+
> | value      | varchar(20) |      |     |         |       |
> | product    | varchar(64) |      |     |         |       |
> | sortkey    | smallint(6) |      |     | 0       |       |
> | product_id | smallint(6) |      |     | 0       |       |
> +------------+-------------+------+-----+---------+-------+
>=20
> However upon further investigation I found that the duplicate values
> were indeed there. The duplicates are all imported data from another
> software package that did not uniquely identify each bug milestone. In
> fact they all had value 0. So I manually changed the data to fix this.
> Ran checksetup again and it errored at another table for similar
> reasons. However the page now seems to be working and you can login,
> edit, query and add new bugs without any issues I have noticed. I am
> just going to try to fix the old bugs to resolve the issues with
sanity
> check and see if everything clears up in the checksetup.
>=20
> Thanks for all your advice.
>=20

Hi Brian.  Based on what I saw in your milestones table, it seems you
have one too many fields.  The product field should not appear there as
product_id refers to the products table where it should be looked up.
Updates to product names are not made in the milestones table, but they
are made in the products table.

One other suggestion you might want to look at - create another Bugzilla
database on your server, and let Bugzilla install itself at the current
version so you can see what things should look like after an upgrade.
That will help you compare table definitions, etc.  It seems like
someone has customized your database for non-Bugzilla "stuff" (see
above).  Having a pristine installation to compare against will help you
isolate what's pure Bugzilla and what's a hybrid.

Good luck. :)

---
Kevin Benton
Perl/Bugzilla Developer/Administrator, Perforce SCM Administrator
Personal Computing Systems Group
Advanced Micro Devices
=20
The opinions stated in this communication do not necessarily reflect the
view of Advanced Micro Devices and have not been reviewed by management.
This communication may contain sensitive and/or confidential and/or
proprietary information.  Distribution of such information is strictly
prohibited without prior consent of Advanced Micro Devices.  This
communication is for the intended recipient(s) only.  If you have
received this communication in error, please notify the sender, then
destroy any remaining copies of this communication.

0
Benton
2/20/2006 8:56:23 PM
Reply: