Closed Bug 711456 Opened 13 years ago Closed 13 years ago

reboot requests (scl1)

Categories

(Infrastructure & Operations :: RelOps: General, task)

Product:
Infrastructure & Operations
Component:
RelOps: General
Type:
task
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: coop, Assigned: dividehex)

References

Details

+++ This bug was initially created as a clone of Bug #710519 +++ talos-r3-fed-017
Assignee: server-ops-releng → jwatkins
colo-trip: --- → scl1
talos-r3-fed64-034
talos-r4-lion-031
talos-r3-fed64-050
talos-r3-fed-026
talos-r3-fed-006
moz2-darwin9-slave53
talos-r3-fed64-030
moz2-darwin9-slave53 belongs in a sjc1 bug :-)
talos-r3-fed-017 | re-imaged talos-r3-fed64-034 | no vga sig talos-r4-lion-031 | re-imaged talos-r3-fed64-050 | no vga sig | re-imaged talos-r3-fed-026 | no vga sig talos-r3-fed-006 | no vga sig | re-imaged talos-r3-fed64-030 | no vga sig | re-imaged
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Alias: reboots-scl1
(In reply to Jake Watkins [:dividehex] from comment #9) > talos-r3-fed-017 | re-imaged > talos-r4-lion-031 | re-imaged > talos-r3-fed64-050 | no vga sig | re-imaged > talos-r3-fed-006 | no vga sig | re-imaged > talos-r3-fed64-030 | no vga sig | re-imaged Jake: so these 5 slaves were re-imaged? Since these slaves will need releng attention after being re-imaged, can you please make sure to open a bug for releng to perform the necessary post-imaging actions for these slaves? FWIW, I'm a fan of the "skip to the re-imaging" step here as that seems like an improvement in turnaround time to me. If that's going to be the new MO, we'll need that follow-up bug filed every time for buildduty to get the re-imaged slaves back into production.
Depends on: 720252
Bug 720252 for the RelEng setup.
Component: Server Operations: RelEng → RelOps
Product: mozilla.org → Infrastructure & Operations
You need to log in before you can comment on or make changes to this bug.