Closed Bug 829126 Opened 13 years ago Closed 12 years ago

[tracker] (Belmont) created MDT-driven automated install configuration for windows 7 test machines

Categories

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

x86
Windows 7
task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: arich, Assigned: q)

References

Details

(Whiteboard: [2013Q3] [tracker] summary on comment 24)

Attachments

(1 file)

This is a tracker bug for creating an MDT installation for w7 tester nodes.
Severity: critical → normal
Assignee: server-ops-releng → qfortier
From CNackers via IRC: I've got an image build for win7 running right now that has all the win8 components, all seemed to install ok... should be able to test and peek at that build tomorrow...
Summary: (Belmont) created MDT-driven automated install configuration for windows 7 test machines → [tracker] (Belmont) created MDT-driven automated install configuration for windows 7 test machines
Whiteboard: [2013Q1] [tracker] → [2013Q2] [tracker]
Blocks: 857064
When we set the machines by hand I followed these steps: https://etherpad.mozilla.org/armenzg-win7 We should probably compare with what we did with Win8 as we had to adjust paths and so.
For some reason I keep on seeing this Window on the foreground of all the test failures I saw on ix-mn-xp-002. I don't know if one of the two happens: 1) after reboot the Windows comes up 2) something inside of the test jobs triggers that window to come up - AFAIK on win7 (and not win8) we change the screen resolution for all test jobs so we could support two types of screen resolutions (with acceleration and without) On another note, we need to install Python2.5 and win32api to this location: C:\\mozilla-build\\python25\\python.exe
I will look into the graphics popup. I have a feeling it is the fakemon.vbs hitting some condition I didn't code for. I will look at the best way to make sure python 2.5 gets to the right place.
Please hold off on the python25 change. It might not be needed. Working on it.
Music to my eyes. I will hold off.
We need to deploy hg 2.5.4 to all test machines (bug 779569) so we will have to include it in our PGO processes.
I noticed a prompt for updates in the notifications area. I would like that to be disabled as well. Please and thanks!
In bug 852915 devs were going to ask us to update the win7 minis to SP1 but I told them to not do so since we're going to have this done by end of the quarter. I've checked the machine I'm using and it has SP1 on it already.
Blockers: 1) disable graphics configuration window (comment 3) 2) disable updates (comment 8) Not needed (fixed with code changes): * Python 2.5 It can be done now or on a follow up: * Update hg to 2.5.4
No longer blocks: win7-ix-releng
ping about ETA; thanks!
Whiteboard: [2013Q2] [tracker] → [2013Q2] [tracker] summary on comment 10 - waiting on 2 imaging issues
Per Amy in etherpad, this will be done by Monday, April 29
(In reply to Armen Zambrano G. [:armenzg] (Release Enginerring) from comment #10) FYI, these have both been resolved: 1) disable graphics configuration window 2) disable updates We are just waiting on the fix with the graphics issue before we can deploy.
Great news! Thanks for the update! Best of luck.
Whiteboard: [2013Q2] [tracker] summary on comment 10 - waiting on 2 imaging issues → [2013Q2] [tracker] summary on comment 10 - waiting on graphic card automation regression
As I spoke with arr on IRC, I will be receiving 10 machines without the dual graphic cards solution in place. This will help me get the machines on staging and determine if the 2 imaging issues that were fixed on comment 13 are the last things needed.
I have put the machines on staging and I will have them in production on Monday as my code did not work and I had to back it out. On another note, could we please deploy "Microsoft Windows Media Feature Pack" to the Win7 machines? We did the same for the Win8 machines on bug 849827. I probably missed reporting this with the mix of all other test failures. Sorry about that. Thanks!
I spoke with arr on IRC and the base Windows 7 does not have to be "Windows 7 *N*", it can actually be the normal Windows 7 base OS. I don't know of any reasons that we would have need to choose that version. Choosing the non-N base OS would mean that the "Microsoft Windows Media Feature Pack" is not needed. My current blocker is fixing this issue.
Whiteboard: [2013Q2] [tracker] summary on comment 10 - waiting on graphic card automation regression → [2013Q2] [tracker] summary on comment 10 - waiting on graphic card automation regression AND Windows Media package
Q added the media feature pack to GPO over the weekend.
Nice! I will try it out.
I have also noticed that IIS is running and it is preventing Apache from working. Could you please disable it? It is preventing us from being able to run Talos jobs. http://cl.ly/OmF3
(In reply to Amy Rich [:arich] [:arr] from comment #18) > Q added the media feature pack to GPO over the weekend. The tests that were failing are now working.
Whiteboard: [2013Q2] [tracker] summary on comment 10 - waiting on graphic card automation regression AND Windows Media package → [2013Q2] [tracker] summary on comment 10 - waiting on graphic card automation regression AND disabling IIS
Found two problems: IIS components that were added after our first testing pass (on the ix- machines) during a devshare mix up and an error in the apache httpd.conf. I has removed IIS in the TS and created a GPO to push out the change to the current machines. I also changed the server root in the httpd.conf file to C:\program files (32 program file path) from C:\program files x86 (64 bit path). Tested on 11 - 13 and the rest of the machines will work after their next reboot.
I have tested that IIS is not on the way anymore. I've triggered one last test for all tests and talos to see if there is anything left.
Whiteboard: [2013Q2] [tracker] summary on comment 10 - waiting on graphic card automation regression AND disabling IIS → [2013Q2] [tracker] summary on comment 10 - waiting on graphic card automation regression
All jobs have passed. The following blockers have been fixed: 1) disable graphics configuration window (comment 3) 2) disable updates (comment 8) 3) Windows Media package deployed (comment 18) 4) Disabled IIS (comment 22) No blockers are left. Fixing the dual graphics solution is important for IT for remote management but we agreed that it will not be blocking the project. It can be resolved after the fact.
Whiteboard: [2013Q2] [tracker] summary on comment 10 - waiting on graphic card automation regression → [2013Q2] [tracker] summary on comment 24
It seems that we get notifications to update the video drivers which I believe it steals focus for some tests (I don't know for sure): https://bugzilla.mozilla.org/attachment.cgi?id=750063&action=edit (bug 872748) Could we disable notifications all together to remove it out of the possible causes?
Grr stupid nvidia. I will look at that and make sure to stop it if it is happening.
Turned off the nvidia update service this should stop the pop-ups according to the doc.
Thanks!
Depends on: 874953
Depends on: 879879
Whiteboard: [2013Q2] [tracker] summary on comment 24 → [2013Q3] [tracker] summary on comment 24
Component: Server Operations: RelEng → RelOps
Product: mozilla.org → Infrastructure & Operations
Anything left on this bug? The general process seems to work wonderfully even if we have the win7 graphics issue still lingering around (I think).
The graphics issue will be solved by us simply not using graphics to install machines.
Status: NEW → RESOLVED
Closed: 12 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: