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)

All
Other
task
Not set
major

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: server-ops → ashish
Shall work with oremj on this once he's online today
@dkl what is your rollback procedure for this upgrade?
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
Push completed. @dkl - could you verify once and then I'll remove extensions/GmailThreading/disabled on all the hosts. Thanks!
All looks good. Please remove the GmailThreading/disabled files. dkl
removed extensions/GmailThreading/disabled on all webheads. @dkl - you can RESOLVE FIXED if it looks good :)
it doesn't look like GmailThreading has been enabled.
(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
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.
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
Blocks: 665501
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.
looks good to me now, thanks :)
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
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
(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 → ---
Blocks: 663562
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.
closing this out.
Status: REOPENED → RESOLVED
Closed: 14 years ago14 years ago
Resolution: --- → FIXED
Component: Server Operations: Web Operations → WebOps: Other
Product: mozilla.org → Infrastructure & Operations
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.