Closed Bug 1403471 Opened 7 years ago Closed 6 years ago

Please run hardware diagnostics on t-w1064-ix-026 and re-image

Categories

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

task
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: aobreja, Unassigned)

References

Details

This machine has a strange behavior,I tried 3 times to re-image it but I'm still not able to finish.The machine eventually remain unreachable,after a reboot become reachable but I'm not able to access it.

Please run hardware diagnostics on it and re-image.
host passed disk diags, going to let memtest run overnight.
Assignee: server-ops-dcops → vle
14 passes and no issues found during memtest. during the reimage i was prompted to continue or start a new deployment. i think this is where the host was stuck at so it never finished imaging for you.


[vle@admin1a.private.scl3 ~]$ fping t-w1064-ix-026.wintest.releng.scl3.mozilla.com
t-w1064-ix-026.wintest.releng.scl3.mozilla.com is alive

however this is appears to have the same problem t-w1064-ix-013 has, where it pings, boots up to the log in page, but im unable to view the IIS page with my laptop browser. any ideas?
>boots up to the log in page

didn't mean page, meant windows log in screen.
nope, the passwords in aspect-low doesn't work for me. is the log in root? 

punting to relops to poke at it since we have another win10 with this exact same problem. also we have another bug [1411094] open indicating the passwords aren't working/correct, probably relevant to this issue.
See Also: → 1411094, 1393482
i changed the video output to onboard so you can ipmi and poke as needed.
Assignee: vle → relops
Component: DCOps → RelOps
QA Contact: cshields → arich
(In reply to Van Le [:van] from comment #5)
> nope, the passwords in aspect-low doesn't work for me. is the log in root? 
> 
> punting to relops to poke at it since we have another win10 with this exact
> same problem. also we have another bug [1411094] open indicating the
> passwords aren't working/correct, probably relevant to this issue.

@dividex - raduiman while on Buildduty shift came across this bug. This and t-w1064-ix-013 are unable to be re-imaged. see comment 2 and comment 5 for more details. Do you know what's going on them? And do we need to update the password known to IT? Worth noting we have enough load capacity for this pool so there isn't an immediate rush.
Flags: needinfo?(jwatkins)
Flags: needinfo?(jwatkins) → needinfo?(mcornmesser)
The automated process to move it from the loaner OU to the production OU did not work. I have moved it, and kicked off the install.
Flags: needinfo?(mcornmesser)
There is a deeper issue here. I will poke at it next week.
Any updates about this machine?
Flags: needinfo?(mcornmesser)
I will close this bug since all w10 tasks now run in taskcluster only. This machine is missing entirely from slave health and will go away together with buildbot at its end of life.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
Flags: needinfo?(mcornmesser)
You need to log in before you can comment on or make changes to this bug.