To all,

Just to give you an update. The planned upgrade of bugzilla from 2.18 to
2.20 on bugs.gentoo.org did not go as planned. A good amount of the
internal database structure behind bugzilla changed from the jump in
stable versions and while running the update script, it crapped out.
Yes, real scientific. Error message is pasted below.[1]

I am in the process of restoring the old database backup I made when I
brought down bugzilla this morning for the upgrade, at which time I
should be bringing up the old bugzilla as soon as possible.

I apologize for over-runing my upgrade window, this is the part I could
not have predicted. 

---- Update within an email

I have restored this morning's DB shapshot when I brought down the
database and restored Bugzilla 2.18 for bugs.gentoo.org.

I will be finding out what the issue is, upon which I will plan some
further downtime.

I apologize profusely for the extended downtime this caused anyone.

Regards,
Jeffrey

[1]
New: varchar(64) NOT NULL
Adding new index 'versions_product_id_idx' to the versions table ...
Adding group editclassifications ...
Adding new index 'attachments_submitter_id_idx' to the attachments
table ...
Adding group bz_canusewhines ...
Adding group bz_canusewhineatothers ...
DBD::mysql::st execute failed: Lost connection to MySQL server during
query [for Statement "SELECT name FROM setting WHERE name = ?"] at
Bugzilla/User/Setting.pm line 207
        Bugzilla::User::Setting::_setting_exists('display_quips') called
at Bugzilla/User/Setting.pm line 120
        Bugzilla::User::Setting::add_setting('display_quips',
'HASH(0xc5c7b38)', 'on') called at ./checksetup.pl line 4081

-- 

-----------------------
Jeffrey Forman
Gentoo Infrastructure
Gentoo Release Engineering
Bugs.Gentoo.org Administrator
[EMAIL PROTECTED]
-----------------------

Attachment: signature.asc
Description: This is a digitally signed message part

Reply via email to