Update AUS2 production for 3.0.13 going to release update channel

RESOLVED FIXED

Status

mozilla.org Graveyard
Server Operations
--
blocker
RESOLVED FIXED
9 years ago
3 years ago

People

(Reporter: nthomas, Assigned: aravind)

Tracking

Details

(Reporter)

Description

9 years ago
+++ This bug was initially created as a clone of Bug #507860 +++

We're shipped 3.0.13 to the relase channel at about 2pm PDT and need to update aus2.m.o's config to un-throttle background checks from older 3.0.x. The config change is described at bug 507633 comment #11 - it's all landed and tagged. Please update the machines behind aus2.m.o to AUS2_PRODUCTION.

[Note to future RelEnger's: we're doing this before pushing the 3.0.13 snippets because the major update got nulled out already, so 3.0.12 doesn't see any update right now.]
(Reporter)

Comment 1

9 years ago
We're *shipping* ...
(Assignee)

Updated

9 years ago
Assignee: server-ops → aravind
(Assignee)

Comment 2

9 years ago
I did an update and didn't seem to pick anything new up.

[root@mradm02 app]# cvs up -dP -r AUS2_PRODUCTION
? inc/config.php
cvs update: Updating .
cvs update: Updating inc
M inc/config-dist.php
[root@mradm02 app]# 

Is that what you expect?
(Reporter)

Comment 3

9 years ago
Are you pulling from cvs-mirror ? Perhaps that's still syncing. M isn't a good sign, should be a clean pull right ?
(Reporter)

Comment 4

9 years ago
inc/config-dist.php should be rev 1.47
(Assignee)

Comment 5

9 years ago
pushed out the changes.  Should sync out in 10 minutes.
Status: NEW → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → FIXED
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.