Closed
Bug 1416222
Opened 7 years ago
Closed 6 years ago
Re-imaging not working for Windows 10
Categories
(Infrastructure & Operations :: RelOps: General, task)
Infrastructure & Operations
RelOps: General
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: aselagea, Assigned: markco)
References
Details
Attachments
(6 files)
Today I tried re-imaging t-w1064-ix-264 since it was failing every job it was taking. Afaik, the onboard graphics card is disabled for Windows 10 and Windows 7, so re-imaging the machine by selecting the proper options in the KVM console is not working. What I tried to do is use ipmitool, meaning two commands: - ipmitool -U releng -P XXXXX -H t-w1064-ix-264-mgmt.inband.releng.scl3.mozilla.com chassis bootdev pxe - ipmitool -U releng -P XXXXX -H t-w1064-ix-264-mgmt.inband.releng.scl3.mozilla.com chassis power reset Both of them seem to be working fine - I can confirm at least the reboot works fine since I monitored the progress using "ping -t". The issue is nothing happens on the machine after reboot, so it doesn't get re-imaged. Checking the original install date using "systeminfo" will show the old installation date. Repeated this process for another Win 10 machine and got the same results. It works fine for Windows 7 though.
Reporter | ||
Comment 1•7 years ago
|
||
cc-ing Q and markco. Is it possible that we are missing some configs for Windows 10 here?
Assignee | ||
Comment 2•7 years ago
|
||
This sounds like the it failing to boot from the network. We hit this issue previously. Today or Monday I will try to dig through the bugs and see what the fix was.
Reporter | ||
Comment 3•6 years ago
|
||
Do we have any updates here? From what I tested, re-images are still not working. e.g. "t-w1064-ix-060" served as a loaner recently and now is no longer needed so it would require a re-image before putting it back in production. I'm guessing this machine can be used to test an eventual fix.
Updated•6 years ago
|
Blocks: t-w1064-ix-101
Comment 4•6 years ago
|
||
Assigning to Mark to dig into after he's got moonshots sorted.
Assignee: relops → mcornmesser
Comment 5•6 years ago
|
||
Comment 6•6 years ago
|
||
Comment 7•6 years ago
|
||
Comment 8•6 years ago
|
||
Comment 9•6 years ago
|
||
The base Win10 returned Bad Task Sequence idem (Missing OS)
Comment 10•6 years ago
|
||
Comment on attachment 8960471 [details]
Screenshot from 2018-03-20 09-37-55.png
Started the reimage with Datacenter Windows 10.
Comment 11•6 years ago
|
||
Comment on attachment 8960468 [details] Screenshot from 2018-03-20 09-25-56.png According to https://mana.mozilla.org/wiki/display/DC/How+To+Reimage+Releng+iX+Windows+Machines there should be MDT Provision x64 and MDT Development x64 but is not.
Comment 12•6 years ago
|
||
Comment on attachment 8960467 [details]
Screenshot from 2018-03-20 09-25-50.png
PXE works fine.
Comment 13•6 years ago
|
||
Looks like the user is root once the reimage almost done, not sure if this is ok, I believe it should be cltbld user.
Updated•6 years ago
|
Flags: needinfo?(mcornmesser)
Comment 14•6 years ago
|
||
Since the machine is not in slavealloc even if I enabled, I believe that the win10 x64 bit image is broken. So, we need someone to check the win10 x64 image and fix it.
Comment 15•6 years ago
|
||
Anyone can restore a older Win10 64 bit image so can try the reimage?
Assignee | ||
Updated•6 years ago
|
Flags: needinfo?(mcornmesser) → needinfo?(q)
Comment 16•6 years ago
|
||
is this machine still needed ? I have checked the slave alloc and slave health >> the machine seems to be disabled. can we close the ticket ?
Flags: needinfo?(mcornmesser)
Assignee | ||
Comment 17•6 years ago
|
||
Since scl3 is going to be decom, I am going to close this bug.
Status: NEW → RESOLVED
Closed: 6 years ago
Flags: needinfo?(mcornmesser)
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•