Closed Bug 1230979 Opened 10 years ago Closed 10 years ago

t-w864-ix-092 is unreachable

Categories

(Infrastructure & Operations :: DCOps, task)

task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: slaveapi, Assigned: van)

References

Details

(Whiteboard: running diags)

No description provided.
host back online [vhua@admin1a.private.scl3 ~]$ ssh t-w864-ix-092.wintest.releng.scl3.mozilla.com The authenticity of host 't-w864-ix-092.wintest.releng.scl3.mozilla.com (10.26.40.122)' can't be established. RSA key fingerprint is aa:7f:de:37:4d:cb:30:e1:38:a2:46:c4:59:75:81:4b. Are you sure you want to continue connecting (yes/no)?
Status: NEW → RESOLVED
colo-trip: --- → scl3
Closed: 10 years ago
Resolution: --- → FIXED
Vinh can you configure ipmi password. I think that's why we keep getting this bug.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
IPMI did not have our default user/pw. I've added them.
Status: REOPENED → RESOLVED
Closed: 10 years ago → 10 years ago
Resolution: --- → FIXED
Well, that's part of it. The other part is that it's broken and needs to go back. It lasted for a job and a half, died, I tried a reboot, and after only an attempt at ssh, still no ipmi, bug 1232565.
I've submit a ticket for iX to take a look. ticket #IPZ-937-83236
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Whiteboard: ticket #IPZ-937-83236
iX ran their diagnostics and did not find any issues. I've swapped out the CAT5 cable and reimaged the host with a spare 1TB drive (no spare 500gb drives atm). Can you see if you can still replicate the issue?
Flags: needinfo?(philringnalda)
It has made it through five jobs, which is quite impressive by its standard.
Status: REOPENED → RESOLVED
Closed: 10 years ago → 10 years ago
Flags: needinfo?(philringnalda)
Resolution: --- → FIXED
this is still under warranty, so if it's a faulty drive, please get another one of the same size from ix. We don't want to mix the drive types in the test pool.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
hard disk RMA ticket #HIB-557-23691
Whiteboard: ticket #IPZ-937-83236 → ticket #HIB-557-23691
picked up hdd from iX and swapped/reimaged. host back online.
Assignee: server-ops-dcops → vle
Status: REOPENED → RESOLVED
Closed: 10 years ago → 10 years ago
Resolution: --- → FIXED
Guess who's "unreachable" again :\
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
:arr, i have the foopie blades which are the same specs sans the memory which i can upgrade. can we replace this blade for one of those as this host should be out OOW by now and is a reoccurring problem.
QA Contact: cshields
Flags: needinfo?(arich)
the foopys were a different CPU, so no, they weren't the same specs.
Flags: needinfo?(arich)
when i removed the blade, i noticed the memory wasn't seated correctly. running a full round of diags and we'll test again. if it still fails, we can swap the CPU and memory over to one of the foopy blades.
Whiteboard: ticket #HIB-557-23691 ticket #HIB-557-23691 → running diags running diags
Howdy, it's been a week, and we're really strapped for capacity. What were the results here?
Ive been in Phoenix for a conference. Can poke when I get back.
memtest ran the week i was gone and it completed 93 passes with no issues. also ran a full disk diags and it came back with no errors. can you give it another whirl?
Status: REOPENED → RESOLVED
Closed: 10 years ago → 10 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.