Closed
Bug 663863
Opened 14 years ago
Closed 14 years ago
Please push code update to bugzilla.mozilla.org and re-enable the GmailThreading extension
Categories
(Infrastructure & Operations Graveyard :: WebOps: Other, task)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: dkl, Assigned: ashish)
References
Details
A fix was committed to the GmailThreading Bugzilla extension that corrected an error where people were not receiving their new account notifications. justdave disabled the extension until a code update could be done which allowed email to work properly again.
Please update the code from the current-staging tag in bmo/4.0 and then remove extensions/GmailThreading/disabled on the web heads.
Thanks
dkl
Assignee | ||
Updated•14 years ago
|
Assignee: server-ops → ashish
Assignee | ||
Comment 1•14 years ago
|
||
Shall work with oremj on this once he's online today
Comment 2•14 years ago
|
||
https://mana.mozilla.org/wiki/display/websites/bugzilla.mozilla.org <- Dave's docs for bugzilla pushes.
Comment 3•14 years ago
|
||
@dkl what is your rollback procedure for this upgrade?
Reporter | ||
Comment 4•14 years ago
|
||
I would assume just updating BZR back to the revision where the current-production tag resides before moving it. It should be documented in justdaves instructions as he normally handles that.
dkl
Assignee | ||
Comment 5•14 years ago
|
||
Push completed.
@dkl - could you verify once and then I'll remove extensions/GmailThreading/disabled on all the hosts.
Thanks!
Reporter | ||
Comment 6•14 years ago
|
||
All looks good. Please remove the GmailThreading/disabled files.
dkl
Assignee | ||
Comment 7•14 years ago
|
||
removed extensions/GmailThreading/disabled on all webheads.
@dkl - you can RESOLVE FIXED if it looks good :)
Reporter | ||
Comment 9•14 years ago
|
||
(In reply to comment #8)
> it doesn't look like GmailThreading has been enabled.
I concur. Something is not right with the extension. Can you verify once more that the disabled file is gone properly?
dkl
Assignee | ||
Comment 10•14 years ago
|
||
I removed the files from all the 6 webheads - pp-app-bugs0{1,2,3} and pm-app-bugs0{3,4,5}. I'll try and catch one of you on IRC on Friday morning.
Reporter | ||
Comment 11•14 years ago
|
||
Ah forgot to mention. Did you do a httpd reload on each of the web heads? It is necessary to preload the extension code into memory when using mod_perl.
dkl
Comment 12•14 years ago
|
||
You don't remove it on the webheads, you remove it on mradm02 and ip-admin02, and then do a push to push it out. Otherwise the next push will re-add it.
Comment 13•14 years ago
|
||
looks good to me now, thanks :)
Reporter | ||
Updated•14 years ago
|
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Comment 14•14 years ago
|
||
The mail queue daemons never picked it up because it wasn't pushed from the admin boxes. Just did that now, should be all working properly shortly.
Group: infra
Comment 15•14 years ago
|
||
(In reply to comment #14)
> The mail queue daemons never picked it up because it wasn't pushed from the
> admin boxes. Just did that now, should be all working properly shortly.
it looks like this hasn't worked:
Received: from bugs01.sj.mozilla.org (bugs01.sj.mozilla.com [63.245.208.220])
by mx.google.com with ESMTP id d17si12058730wbh.8.2011.06.27.12.58.37;
Mon, 27 Jun 2011 12:58:38 -0700 (PDT)
Subject: [Bug 667587] New: [PN]AMO Give zamboni /developers/docs
Received: from bugzilla01.phx.mozilla.com (bugzilla01.phx.mozilla.com [63.245.216.221])
by mx.google.com with ESMTP id m3si35431000icx.4.2011.06.27.11.32.05;
Mon, 27 Jun 2011 11:32:05 -0700 (PDT)
Subject: [Bug 667543] Update builder.addons.mozilla.org on 6/29 @ 1400
emails from sj still contain the "new: " marker, however emails from phx do not.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Assignee | ||
Comment 16•14 years ago
|
||
Yes, the SJC hosts hadn't gotten the update. I removed the disabled file on mradm02, re-pushed it and it reflects correctly on all the webheads.
I'll keep the bug open for verification.
justdave - during the push, one of the boxes got a "errno=Connection refused" from git but it was intermittent when i did a couple of dry-runs from the host though. a re-push didn't get the error.
Assignee | ||
Comment 17•14 years ago
|
||
closing this out.
Status: REOPENED → RESOLVED
Closed: 14 years ago → 14 years ago
Resolution: --- → FIXED
Updated•11 years ago
|
Component: Server Operations: Web Operations → WebOps: Other
Product: mozilla.org → Infrastructure & Operations
Updated•6 years ago
|
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•