Closed Bug 1446994 Opened 6 years ago Closed 5 years ago

t-w732-ix-117 is unreachable

Categories

(Release Engineering :: General, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: slaveapi, Assigned: q)

References

Details

Attachments

(3 files)

      No description provided.
Hey Sir Van Lee, do you think this machine needs a re-image like the previous win7 machines you recently fixed? 
It's enabled however it hasn't taken a job since June 12th, 2017. Maybe it needs new hardware too?
Flags: needinfo?(vle)
:zsoltfay/:arny, this host locks up after pxebooting while trying to download the image from the imaging server. ive enabled onboard video, can you guys use the virtual kvm and take a look? if all else fails, we can use a decommissioned XP machine to replace this one or we'll have to decommission this host.
Assignee: server-ops-dcops → vle
Flags: needinfo?(zfay)
Flags: needinfo?(vle)
Flags: needinfo?(acraciun)
I believe this server has a bad HDD. While is set to boot from HDD, there is a error saying: A disk read error occurred.

Please replace the HDD and then we'll try the re-image.
Flags: needinfo?(acraciun)
Flags: needinfo?(zfay)
Attached image New error
host is out of warranty but i was able to find a spare. i tried imaging it again but i am getting new errors about now being to inject the drivers. can you guys IPMI in and take a look?
Flags: needinfo?(zfay)
>i tried imaging it again but i am getting new errors about now being to inject the drivers.

unable to inject the drivers*
The pxe image is not the correct one. 

The correct boot list should look like https://mana.mozilla.org/wiki/download/attachments/35068152/production-x86-deploy-share.jpg
does this mean the host is not in the correct OU? this isn't something that i can fix on my end.
Flags: needinfo?(acraciun)
So i'm guessing we should escalate it more. Who has more knowledge /experience in this?
Flags: needinfo?(zfay)
markco/q, is this something you can assist with?
Flags: needinfo?(q)
Flags: needinfo?(mcornmesser)
looks like it is not finding the PTR record for t-w732-ix-117 so the machine can't find its task sequence or machine name. I supplied both for the time being to see if the install completes
Flags: needinfo?(q)
the installation failed again.
Please swap the disk with another one, I have tried to manual format and gives me error. I think there is still a broken HDD on this server.
Flags: needinfo?(acraciun)
found another spare drive. still getting the old boot menu.
Yeah, at least windows is installing now. I have installed the Base win7.

Not sure why the win7 re-image is not working anymore, it was fine 3-4 weeks ago when I used to re-image some win7 machines. Maybe is just better to disable this servers.
Van: Could you change the graphic card priority in the BIOS for this machine? I will do some trouble shooting after that is done.
Flags: needinfo?(mcornmesser)
Flags: needinfo?(vle)
Mark: I think the issue is at the image server (wds1.releng.ad.mozilla.com - 10.22.69.26), you should check that why is not delivering the correct deploy image as is shown in https://mana.mozilla.org/wiki/download/attachments/35068152/production-x86-deploy-share.jpg .
:markco, the host is currently set to onboard video so you can use IPMI. did you want it to set back to the external video card?
Flags: needinfo?(vle) → needinfo?(mcornmesser)
Perfect. I will take a look at it today.
Flags: needinfo?(mcornmesser)
This isn't the WDS server. This is the DHCP server the DHCP server was serving a special 32bit installer image to allow automation and we are not getting that image. Was there a change to DHCP recently in SCL3? We can do the image without it with some manual intervention.
Also we have dropped support for windows 7 in mdc1 and mdc2 so 32 changes aren't need there only for dhcp entries in SCL3
>Was there a change to DHCP recently in SCL3?

yes, 2 weeks ago we had a maintenance to have infoblox handle the dhcp and dns requests in SCL3.
2 things were happening here. 1st, network was selected as the 1st in the boot order. 2nd the machine was defaulting the provisioning share preinstall environment. Which has several pieces "broken" for testing and development of the OCC images. That is why the name was not being set. The reason why it was being defaulted to was it was first in the list available options. 


Q: When I look into wds1 windows deployment services -> boot images, it shows all the preinstall environments at the same priority. If I go to change the priority it get a message that the images has not ID assigned. Any ideas?
Flags: needinfo?(q)
Sorry, I have no idea, however, If I get access there maybe I can do some tests.
Try this, maybe it helps

This happens after you migrate your WDS server by copying the REMINST folder.

All you need to do to have IDs assigned to your install images is:

1 - Export each image (or just the ones you need to have ID assigned to.

2 - Replace the image with the one you've just exported

3 - Go to the image's properties windows and click OK (this step might not be necessary; sometimes it is, sometimes it isn't, go figure...)

Done! Now you can change the priority value.

You don't need to change anything, the newly imported image will retain all the descriptions it previously had. Exporting can take a while, importing is almost instantly.

If you export several images into the same file, exporting will be very quick aswell. I exported all the images into the same file. Each export was quicker than the previous one, if they're all based on the same OS version.


from: https://social.technet.microsoft.com/Forums/windowsserver/en-US/e1472796-916f-4bdb-8a3b-0a474fdb1183/wds-2012-image-priority-error-the-specified-image-has-no-id-assigned?forum=winserversetup#e1472796-916f-4bdb-8a3b-0a474fdb1183
hi, any updates? re: c#25, i dont have access to perform the changes and the process would need to be reviewed by :markco/:q.
This is specifically a problem with DHCP options. If we review the the DCHP options in legacy inventory for a windows 7 machine you find a dhcp boot file being set that was rigged to boot windows 7. A filter must be created in infoblox to give out that bootfile for windows 7 machines.

Q
Flags: needinfo?(q)
punting to releng for traction.
Component: DCOps → General
Product: Infrastructure & Operations → Release Engineering
QA Contact: cshields → catlee
Assignee: vle → nobody
fubar, can you help resolve this?
Flags: needinfo?(klibby)
We're not likely to re-instate the ability to pxeboot w32 systems in SCL3; it would require a bunch of work that we're just going to dismantle in two months. If XP systems suddenly have issues, I'd revisit that, but we've got ~145 idle t-w732-ix systems atm, so marking this one as dead and moving on seems like the best approach. I'm open to opposing view points, however.
Flags: needinfo?(klibby)

With the SCL3 decomm this is no longer and issue. Moving forward we are no longer supporting windows 7 on hardware only in cloud. MY apologies that closing this ticket came from attrition instead of action

Assignee: nobody → q
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: