Closed
Bug 908184
(production-opsi)
Opened 11 years ago
Closed 11 years ago
production-opsi problem tracking
Categories
(Infrastructure & Operations Graveyard :: CIDuty, task)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: armenzg, Unassigned)
Details
We want to keep it off and decommission it once the talos-r3-xp-* and mw32-ix-* are decommissioned. We want to see if our systems will keep on running without it. production-opsi:~# shutdown -h -P now The system is going down for system halt NOW!pts/1) (Thu Aug 22 15:42:39 2013 production-opsi:~# Connection to production-opsi closed by remote host. Connection to production-opsi closed.
Reporter | ||
Comment 1•11 years ago
|
||
dustin, if I needed to start up the host later today, what is way of doing it? I tried loading the OOB IP that inventory tells me about but the page is not reachable for me.
Comment 2•11 years ago
|
||
It's a VMware host, so someone with vCenter access can do so. gcox/lerxst or oncall are a good bet.
Reporter | ||
Comment 3•11 years ago
|
||
From looking at these: https://secure.pub.build.mozilla.org/builddata/reports/slave_health/slavetype.html?class=build&type=mw32-ix https://secure.pub.build.mozilla.org/builddata/reports/slave_health/slavetype.html?class=test&type=talos-r3-xp I don't see *all* xp machines out of action. The mw32 have not taken jobs for 27 days so it is hard to tell. Let's keep the machine off but don't delete until the mw32-* and talos-r3-xp-* are decommissioned. Is this OK with you?
Flags: needinfo?(dustin)
Comment 5•11 years ago
|
||
This host is in the expected state (offline). I'm closing this because there's no problem to track.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Reporter | ||
Updated•10 years ago
|
Assignee: armenzg → nobody
QA Contact: armenzg → bugspam.Callek
Updated•6 years ago
|
Product: Release Engineering → Infrastructure & Operations
Updated•4 years ago
|
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•