Closed Bug 575307 Opened 14 years ago Closed 14 years ago

[Tracking bug] Unscheduled downtime for the week of June 28 - July 2 2010

Categories

(Release Engineering :: General, defect)

Product:
Release Engineering
Component:
General
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: jhford, Assigned: jhford)

References

Details

Please make any bugs that need a downtime this week block this bug.
OS: Mac OS X → All
Hardware: x86 → All
Summary: Downtime for the week of June 28 - July 2 → [Tracking bug] Unscheduled downtime for the week of June 28 - July 2 2010
adding bug 574538 to add a second cpu to test-master01
Depends on: 574538
Depends on: 574062
Adding bug 573999 to make mar generation steps conditional on finding a previous complete mar.
Depends on: 573999
Depends on: 559929
Depends on: 573503
No longer depends on: 573503
Assignee: nobody → jhford
downtime plan:
-land addons patch
-land remove1.9.0 patch
-reconfig talos-master02
-list current jobs on test-master01
-shutdown test-master01 to add cpu
-start test-master01
-rekick current jobs on test-master01
-land mar generation patch
-land build space patch
-land addonsmgr removal
-reconfig pm01, pm02-try, pm03
(In reply to comment #3)
> downtime plan:
> -land addons patch
> -land remove1.9.0 patch
> -reconfig talos-master02
> -reconfig test-master01
> -land mar generation patch
> -land build space patch
> -land addonsmgr removal
> -reconfig pm01, pm02-try, pm03

Punting on test-master01 restart for this downtime.
No longer depends on: 574538
(In reply to comment #4)
> Punting on test-master01 restart for this downtime.

Clarified on IRC that it is ok to kill the running jobs on test-master01
Depends on: 574538
test-master01 restart + reconfig done
talos-master02 reconfig done
pm01.scheduler reconfig done
pm01.builder reconfig done
pm03.buidler reconfig done

Reopening the tree
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Alias: releng-downtime
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.