Migration of customized bugzilla 2.12 to bugzilla 3.6

Hello All,

    We have modified the bugzilla 2.12 to facilitate the requirements of
the company. But since it's a very old code base and we want to be in
sync with the current bugzilla release we want to migrate.

=20

So our first step is to migrate the data.

=20

The current customized bugzilla database dosen't have any references

=20

Steps I followed was as per the instructions. Please correct me and
provide me your suggestions

=20

1)      Took the dump and restored it

2)      Downloaded the tar ball and extracted

3)      Ran the checksetup.pl and configured the localconfig file

=20

Results that came out was

=20

1)      Converted the MyIsam engine of the tables to InnoDB

2)      Asked to removed all fulltext indexes

3)      Told to run recode.pl to convert it to UTF-8

4)      Then again ran checksetup.pl

5)      Converted all tables to utf-8 charset

6)      The unique id names were renamed

7)      Primary keys were added but no foreign keys got added

8)      Website was not up as the new columns that should be added were
not added. For example isActive did not get added to the products table.

=20

So please suggest what is the process that I should follow for  smooth
migration.

=20

Do I need to migrate to intermediate bugzilla installations and then to
3.6

=20

Your reply will be very much helpful

=20

Thanks

Subodh Konhor

0
Konhor
6/10/2010 1:24:36 PM
mozilla.support.bugzilla 10162 articles. 0 followers. Post Follow

7 Replies
657 Views

Similar Articles

[PageSpeed] 15

Le 10. 06. 10 15:24, Konhor, Subodh a �crit :
> Do I need to migrate to intermediate bugzilla installations and then to
> 3.6

Migrating from Bugzilla 2.12 to 3.6 should work just fine, assuming your
DB schema matches what checksetup.pl expects for 2.12. If not, then you
are probably in trouble.

LpSolit
0
ISO
6/10/2010 9:22:30 PM
Hi Raghu,

          Thanks for responding and the exhaustive steps that you have
given.=20

Currently as per my plan I was thinking of migrating the data and making
the bugzilla 3.6 functional.

=20

So I ran the checksetup.pl without modifying the code base. I was able
to migrate the data=20

=20

1)      I got warnings while converting the data in attachments table
like

a.       Warning - could not determine correct creation time for
attachment 413  on bug 4818

2)      After the data was migrated when I opened mybugs or viewing bugs
it gave the below error

=20

undef error - The 'name' parameter (undef) to DateTime::TimeZone::new=20

> was an 'undef', which is not one of the allowed types: scalar at=20

> /usr/local/share/perl/5.8.8/Params/ValidatePP.pm line 630=20

> Params::Validate::__ANON__('The \'name\' parameter (undef) to=20

> DateTime::TimeZone::new was...') called at=20

> /usr/local/share/perl/5.8.8/Params/ValidatePP.pm line 484=20

> Params::Validate::_validate_one_param('undef', 'HASH(0x95ab5e0)',=20

> 'HASH(0x95ab598)', 'The \'name\' parameter (undef)') called at=20

> /usr/local/share/perl/5.8.8/Params/ValidatePP.pm line 353=20

> Params::Validate::validate('ARRAY(0x847a698)', 'HASH(0x95ab5b0)')

called

> at lib/DateTime/TimeZone.pm line 34 DateTime::TimeZone::new('undef',=20

> 'name', 'undef') called at Bugzilla/User.pm line 391

> Bugzilla::User::timezone('Bugzilla::User=3DHASH(0x939bb78)') called at =


> Bugzilla/Util.pm line 480 Bugzilla::Util::datetime_from('2010-02-10

> 15:14:52', 'undef') called at Bugzilla/Util.pm line 434=20

> Bugzilla::Util::format_time('2010-02-10 15:14:52', 'undef', 'undef')=20

> called at Bugzilla/Template.pm line 625=20

> Bugzilla::Template::__ANON__('2010-02-10 15:14:52') called at=20

> template/en/default/bug/show-header.html.tmpl line 46 eval {...}

called

> at template/en/default/bug/show-header.html.tmpl line 12

>=20

Template::Provider::__ANON__('Bugzilla::Template::Context=3DHASH(0x92e890=
c

> )') called at lib/i486-linux-gnu-thread-multi/Template/Document.pm

line

> 151 eval {...} called at

> lib/i486-linux-gnu-thread-multi/Template/Document.pm line 149=20

> Template::Document::process('Template::Document=3DHASH(0x961b4cc)',

> 'Bugzilla::Template::Context=3DHASH(0x92e890c)') called at=20

> lib/i486-linux-gnu-thread-multi/Template/Context.pm line 351 eval

{...}

> called at lib/i486-linux-gnu-thread-multi/Template/Context.pm line 321

>=20

Template::Context::process('Bugzilla::Template::Context=3DHASH(0x92e890c)=
'

> , 'bug/show-header.html.tmpl') called at Bugzilla/Template/Context.pm=20

> line 45

>=20

Bugzilla::Template::Context::process('Bugzilla::Template::Context=3DHASH(=
0

> x92e890c)', 'bug/show-header.html.tmpl') called at=20

> template/en/default/bug/show.html.tmpl line 30 eval {...} called at=20

> template/en/default/bug/show.html.tmpl line 18

>=20

Template::Provider::__ANON__('Bugzilla::Template::Context=3DHASH(0x92e890=
c

> )') called at lib/i486-linux-gnu-thread-multi/Template/Document.pm

line

> 151 eval {...} called at

> lib/i486-linux-gnu-thread-multi/Template/Document.pm line 149=20

> Template::Document::process('Template::Document=3DHASH(0x95ea12c)',

> 'Bugzilla::Template::Context=3DHASH(0x92e890c)') called at=20

> lib/i486-linux-gnu-thread-multi/Template/Context.pm line 351 eval

{...}

> called at lib/i486-linux-gnu-thread-multi/Template/Context.pm line 321

>=20

Template::Context::process('Bugzilla::Template::Context=3DHASH(0x92e890c)=
'

> , 'Template::Document=3DHASH(0x95ea12c)') called at=20

> Bugzilla/Template/Context.pm line 45

>=20

Bugzilla::Template::Context::process('Bugzilla::Template::Context=3DHASH(=
0

> x92e890c)', 'Template::Document=3DHASH(0x95ea12c)') called at=20

> lib/i486-linux-gnu-thread-multi/Template/Service.pm line 94 eval {...}


> called at lib/i486-linux-gnu-thread-multi/Template/Service.pm line 91=20

> Template::Service::process('Template::Service=3DHASH(0x86374c0)',

> 'bug/show.html.tmpl', 'HASH(0x8153c28)') called at=20

> lib/i486-linux-gnu-thread-multi/Template.pm line 66=20

> Template::process('Bugzilla::Template=3DHASH(0x91e64b4)',

> 'bug/show.html.tmpl', 'HASH(0x8153c28)') called at=20

> /home/subodh/mdump/bugzilla-3.6/show_bug.cgi line 128

=20

Could you tell me what is the exact reason for the above warning and
error or any pointer that will be helpful.

=20

Thanks

Subodh Konhor

0
Konhor
6/22/2010 3:33:04 PM
Hi All,

   After the Data migration and BZ 3.6 is operational, the next task for
me is to customize Bugzilla 3.6 for having customization to be added.
Since we have customized bugzilla 2.12, will the plain merge work or do
I have to rewrite the functionality? As of now I am not too  familiar
with the code base of Bugzilla 3.6.

=20

Thanks

Subodh Konhor

0
Konhor
7/1/2010 1:45:26 PM
Hello All,

=20

 Since I am migrating bugzilla 2.12 to 3.6  I need to run both the
systems in parallel for some time . This is for falling back to the old
system if 3.6 doesn't work out or some issue. Is there a way I can keep
bugzilla 2.12 and bugzilla 3.6 in sync i.e the new data getting
replicated on either version.

=20

Has someone run two versions of bugzilla in parallel.

=20

Thanks

Subodh Konhor

0
Konhor
7/6/2010 10:02:06 AM
This is a multi-part message in MIME format.

------_=_NextPart_001_01CB234D.8850B7B8
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi All,

     I have this doubt on the workflow behavior of Bugzilla 3.6. When I
create a new bug the bug is created as Assigned. I am not able to change
the initial status as new in the admin section. The other thing is, in
my earlier database I had many bugs which are new. When I open that, in
the show bug page the bug status is new but the resolution dropdown
becomes active which has default value as fixed.=20

=20

=20

=20

So when I save changes the bug now has status like NEW FIXED which is
incorrect. Ideally it should not show the resolution part itself when
the status is NEW.=20

=20

Changes I have made in the admin section is I have disabled sending
mail.

=20

Waiting for a reply

=20

Thanks

Subodh Konhor


------_=_NextPart_001_01CB234D.8850B7B8--
0
Konhor
7/14/2010 12:10:16 PM
Hi All,

       The current interface gives us the option to add custom fields
from the interface.=20

1)      Now suppose I have to add new fields to be entered while bug
creation, should I do it from the Custom fields section or manually make
database changes and write code to handle it.=20

2)      My earlier bugzilla database from which I migrated has many new
fields added to the bugs table and those are added to the fielddefs
table

a.       Should I rename them all with prefixing "cf_".

b.      Should I make those all editable by setting the custom value to
1.

c.       In the earlier database there are some columns added to bugs
table but those entries are not done in the fielddefs table. Should that
be done now?

3)      The migrated database doesn't have any STATUS as UNCONFIRMED nor
any of my bugs are in that state. Should I add the "UNCONFIRMED" status?

=20

Thanks in advance

=20

Subodh Konhor

0
Konhor
7/20/2010 8:05:02 AM
Sending it to you as the mailing list is down or is not accepting any
mails

=20

Below is my doubt

=20

 The current interface gives us the option to add custom fields from the
interface.=20

1)      Now suppose I have to add new fields to be entered while bug
creation, should I do it from the Custom fields section or manually make
database changes and write code to handle it.=20

2)      My earlier bugzilla database from which I migrated has many new
fields added to the bugs table and those are added to the fielddefs
table

a.       Should I rename them all with prefixing "cf_".

b.      Should I make those all editable by setting the custom value to
1.

c.       In the earlier database there are some columns added to bugs
table but those entries are not done in the fielddefs table. Should that
be done now?

3)      The migrated database doesn't have any STATUS as UNCONFIRMED nor
any of my bugs are in that state. Should I add the "UNCONFIRMED" status?

=20

Thanks in advance

=20

Subodh Konhor

=20

0
Konhor
7/20/2010 12:33:54 PM
Reply:

Similar Artilces:

Upgrade Bugzilla 2.22.3 to Bugzilla 3.4.6 under Windows-XP. #2
This is a multi-part message in MIME format. ------=_NextPart_000_0043_01CB059F.E89B4560 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: quoted-printable Hello, =20 * I=92m using the Bugzilla-2.22.3 under Windows-XP and would like upgrading to new release of Bugzilla-3.4.6 (also under Windows-XP).=20 =20 * I have followed the instructions of the following (correspondingly to Windows-XP): http://www.bugzilla.org/docs/3.4/en/html/upgrade.html.=20 =20 * I have installed the full required Perl-modules regarding the output of checks...

Restoring Bugzilla 3.2 mysql backup on bugzilla 3.6.3 mysql
Hi Everyone - * Installed Bugzilla 3.6.3 on new machine * Took the MYSQL backup from old Bugzilla 3.2. * Restored the MYSQL back up on Bugzilla 3.6.3, now while login I a= m getting: Software error: DBD::mysql::db do failed: Column 'ipaddr' cannot be null [for Statement "IN= SERT INTO logincookies (cookie, userid, ipaddr, lastused) VALUES (?, ?, ?, NOW())"] at Bugzilla/Auth/Persist/Cookie.pm = line 66 Bugzilla::Auth::Persist::Cookie::persist_login('Bugzilla::Auth::Per= sist::Cookie=3DHASH(0x2a709b4)', ...

[BUGZILLA] Vulnerabilities in Bugzilla 2.16.6 and 2.18rc2 #3
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Bugzilla Security Advisory October 24, 2004 Summary ======= Bugzilla is a Web-based bug-tracking system, used by a large number of software projects. This advisory covers three security bugs that have recently been discovered and fixed in the Bugzilla code: In the stable 2.16 releases, it is possible to make a specific change to a bug without permissions; and in the 2.18 release candidate, there are information leaks with private attachments and comments. We are not aware of any occasions where any of these vulnerabilities h...

Migrating Bugzilla 2.20 to Bugzilla 3
Hi everyone, I'm new in the list but I'd like to say how such a good work you have done on this version of Bugzilla. I'm using bugzilla 2.20 but tried to upgrade it to bugzilla 3 but unfortunately just export the database of Bugzilla 2.20 to Bugzilla 3 database didn't worked. I'm looking for at web but I've get any result yet. Thanks, -- Leonardo A. M. dos Santos HST Sistemas & Tecnologia Service Desk - Fábrica de Softwares Fone: +55 19 3294-0331 www.hst.com.br ...

Problem migrating database from bugzilla 2.20.2 to bugzilla 3.0
hi all, I installed bugzilla 3.0 and was working fine till I tried migrating the mysql db from previous version of bugzilla 2.20.2. These two versions are on different machines. I created .dmp file to get the data in bugzilla 2.20.2 to update it to bugzilla 3.0. Tables seemed to be updated(not sure if there is mismatch between the table structure), but after that upon trying to run checksetup.pl script, I am getting the following message ------------------------------------------------ "There was an error connecting to MySQL: Access denied for user 'bugs'@'localh...

Upgrade Bugzilla 2.22.3 to Bugzilla 3.4.6 under Windows-XP.
Hi All, * We are using the Bugzilla 2.22.3 under Windows-XP and would like upgrading to new release of Bugzilla 3.4.6 (also under Windows-XP). * I have followed the instructions of the following (correspondingly to Windows-XP): http://www.bugzilla.org/docs/3.4/en/html/upgrade.html * Unfortunately this upgrade process is not working, maybe because of this upgrade process will work only if the Bugzilla server installed on Linux or Solaris? * I got the following error when tried to access to the Bugzilla server (after the upgrade process): Software error...

[ANN] Release of Bugzilla 4.1.3, 4.0.2, 3.6.6, and 3.4.12
Today we are releasing 4.0.2, 3.6.6, 3.4.12, and the unstable development snapshot 4.1.3. All of today's releases contain security fixes. We recommend all Bugzilla administrators read the Security Advisory linked below. 4.0.2 is our latest stable release, containing various useful bug fixes and performance improvements. 3.6.6 and 3.4.12 are security updates for those series. Note that 4.1.3 is an unstable development release and should not be used in production environments. We are feature-frozen at this point, however, so the features you see in 4.1.3 shoul...

[ANN] Security Advisory for Bugzilla Versions Prior to 3.4.12, 3.6.6, 4.0.2, and 4.1.3
Summary ======= Bugzilla is a Web-based bug-tracking system used by a large number of software projects. The following security issues have been discovered in Bugzilla: * Internet Explorer 8 and older, and Safari before 5.0.6 do content sniffing when viewing a patch in "Raw Unified" mode, which could trigger a cross-site scripting attack due to the execution of malicious code in the attachment. * It is possible to determine whether or not certain group names exist while creating or updating bugs; and in Bugzilla 4.1.1 and 4.1.2, also by using custom se...

[BUGZILLA] Vulnerabilities in Bugzilla 2.16.6 and 2.18rc2 #2
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Bugzilla Security Advisory October 24, 2004 Summary ======= Bugzilla is a Web-based bug-tracking system, used by a large number of software projects. This advisory covers three security bugs that have recently been discovered and fixed in the Bugzilla code: In the stable 2.16 releases, it is possible to make a specific change to a bug without permissions; and in the 2.18 release candidate, there are information leaks with private attachments and comments. We are not aware of any occasions where any of these vulnerabilities h...

Migrating from Bugzilla 2.18/MySQL 4.1.11 to Bugzilla 2.22/Postgres 8.1.3
What is the best way to migrate a bugzilla installation 2.18/MySQL 4.1.11 on machine A to a bugzilla installation 2.22/Postgres 8.1.3 on machine B? Thanks, Ey�un E. Jacobsen On Wed, 2006-04-26 at 00:25 +0100, "Eyðun E. Jacobsen" wrote: > What is the best way to migrate a bugzilla installation 2.18/MySQL > 4.1.11 on machine A to a bugzilla installation 2.22/Postgres 8.1.3 on > machine B? 1. Upgrade the MySQL/2.18 to 2.22. (Follow the upgrade instructions in the release notes.) 2. Run checksetup in a Pg version of 2.22. 3. Use contrib/bzdbcopy.pl. ...

Testopia 1.3 (Bugzilla 3.0) and Testopia 1.2.2 (Bugzilla 2.22.x) Released
Testopia 1.3 has been released.=20 This Testopia is compatible with Bugzilla 3.0 and mod_perl and provides Postgres support. For those of you still running Bugzilla 2.22.x, I am also releasing 1.2.2 which is a (major) bug fix release. They are available from the project home page at http://www.mozilla.org/projects/testopia Thanks for all the feedback. Keep it coming. Greg Hendricks ...

How to upgrade Bugzilla 2.22 to Bugzilla 3.2
Hi All, Could some one guide me to upgrade Bugzilla 2.22 to Bugzilla 3.2.2 What are the steps to upgrade. Regards Nilesh ...

[ANN] Security Advisory for Bugzilla 3.2.6, 3.4.6, 3.6, and 3.7
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Summary ======= Bugzilla is a Web-based bug-tracking system used by a large number of software projects. The following security issues have been discovered in Bugzilla: * Everybody could search for time-tracking information, not just members of the timetrackinggroup. * Under suexec, "localconfig" was world-readable, meaning that local users with shell access to the Bugzilla server may have been able to see the database password and the site_wide_secret. All affected installations are encouraged to upgrade as so...

Issue With Migrating Bugzilla 3.0.5 to Bugzilla 4.0.2
ERROR: There are invalid values for the assigned_to column in the bugs table. (These values do not exist in the profiles table, in the userid column.) Before continuing with checksetup, you will need to fix these values, either by deleting these rows from the database, or changing the values of assigned_to in bugs to point to valid values in profiles.userid. The bad values from the bugs.assigned_to column are: 13, 16, 22, 23, 38, 40 On 01/12/11 11:33, Krishnaraj B wrote: > ERROR: There are invalid values for the assigned_to column in the bugs > table. (These values do not exist...