Closed Bug 660303 Opened 13 years ago Closed 13 years ago

decommission talos-r3-xp-067-BROKEN

Categories

(Infrastructure & Operations Graveyard :: Servicedesk, task)

Product:
Infrastructure & Operations Graveyard
Component:
Servicedesk
Type:
task
Priority:
Not set
Severity:
minor

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: dustin, Assigned: hlangi)

Details

(Whiteboard: [buildslaves]) 

This was detected in bug 658414.
Assignee: server-ops-releng → zandr
colo-trip: --- → scl1
The machine is already in MV. No colo trip required.
colo-trip: scl1 → ---
Assignee: zandr → mlarrain
Severity: normal → minor
What would you like me to do with this machine?
This should go to desktop for repair.
Did this get sent to Desktop?
Requires zandr to inform on location of machine.
Status: NEW → ASSIGNED
giving to desktop to send for repair
Assignee: mlarrain → hlangi
Component: Server Operations: RelEng → Server Operations: Desktop Issues
QA Contact: zandr → tfairfield
I got this back from wefixmacs, the logic board needs to be replaced which is not cost effective.
Assignee: hlangi → mlarrain
Component: Server Operations: Desktop Issues → Server Operations: RelEng
QA Contact: tfairfield → zandr
Summary: I/O error on talos-r3-snow-051 → decommission talos-r3-snow-051
Assignee: mlarrain → jwatkins
Assignee: jwatkins → mlarrain
Machine is now known as talos-r3-xp-067
Summary: decommission talos-r3-snow-051 → decommission talos-r3-xp-067
no, it's known as talos-r3-xp-067-BROKEN
Summary: decommission talos-r3-xp-067 → decommission talos-r3-xp-067-BROKEN
Machine has been removed from Nagios, DHCP, DNS and inventory. Assigning to Desktop to finish off.
Assignee: mlarrain → hlangi
Component: Server Operations: RelEng → Server Operations: Desktop Issues
QA Contact: zandr → tfairfield
Closing this out.
Status: ASSIGNED → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
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.