Closed
Bug 1205655
Opened 9 years ago
Closed 9 years ago
t-w864-ix-092 is unreachable
Categories
(Infrastructure & Operations :: DCOps, task)
Infrastructure & Operations
DCOps
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: slaveapi, Unassigned)
References
Details
(Whiteboard: bad eth0 - #UDX-455-57764)
Attachments
(1 file)
73.52 KB,
image/png
|
Details |
No description provided.
Comment 1•9 years ago
|
||
found the host up yesterday, reachable via ssh and ipmi. i gave it another quick reimage to see if it was the image causing an issue. came back to this error.
Comment 2•9 years ago
|
||
Sounds like it need some hardware diags.
Updated•9 years ago
|
colo-trip: --- → scl3
Comment 4•9 years ago
|
||
passed memtest, now running hd diags
Whiteboard: running diagnostics → running hdd diags
Comment 5•9 years ago
|
||
HDD diags did not detect any issues. Reimaging host
Whiteboard: running hdd diags → reimaging in progress
Comment 6•9 years ago
|
||
reimaging failed, looks like bad eth0
Whiteboard: reimaging in progress → bad eth0
Comment 8•9 years ago
|
||
false alarm, nic0 works after a few reboots. Host reimaged. vhua$ 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 42:48:e3:21:bf:a3:02:d0:88:88:3f:66:7c:9a:1a:7d. Are you sure you want to continue connecting (yes/no)?
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Comment 10•9 years ago
|
||
And then I (perhaps prematurely) rebooted it, and got another unreachable filed.
Comment 11•9 years ago
|
||
Rebooted the host via IPMI. It's up now. vhua$ 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 42:48:e3:21:bf:a3:02:d0:88:88:3f:66:7c:9a:1a:7d. Are you sure you want to continue connecting (yes/no)?
Comment 12•9 years ago
|
||
This time instead of doing the preventative reboot while it was still disabled, to clear up possible resolution troubles from it having had a monitor attached, I just reenabled it and rebooted it, and got a successful reboot. We'll see :)
You need to log in
before you can comment on or make changes to this bug.
Description
•