Closed Bug 1401007 Opened 7 years ago Closed 7 years ago

Ensure generic worker runs on Windows Server 2016

Categories

(Taskcluster :: Workers, enhancement)

Product:
Taskcluster
Component:
Workers
Type:
enhancement
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: coop, Unassigned)

References

Details

As part of getting the new AMI setup in bug 1401004, we'll want to make sure the generic worker functions on the new platform. Greg suggested Pete as a potential resource here.

Timeline for the new AMI is late Q4/early Q1, per bug 1401004.
I'm creating an experimental "win2016" worker type in the above commit to see how things play out.

For fun, I've created an NSS build task to run against it:

  * https://tools.taskcluster.net/groups/fDB0IaGBS22ptvjR4VDmsw/tasks/fDB0IaGBS22ptvjR4VDmsw/details

The chance of the AMI building correctly, the worker installing and being configured correctly, the task getting run and all scopes being correct, is extremely small, so I imagine this will require a few iterations.

But it is at least a fixed point to aim for. :-)
False alarm: although called win2016, that was actually a win2012r2 AMI (I coped win2012r2 worker type definition, then ran update to refresh AMIs, but task was triggered before rollout completed, so ran against win2012r2 AMIs).

AMI rollout now completed, so triggering a new test task:

  * https://tools.taskcluster.net/groups/V-AKZsfqQgy6iTGSNedIuA/tasks/V-AKZsfqQgy6iTGSNedIuA/details
I don't quite believe it, but it seems to have worked! :)

Note, we'll probably want to create gecko-{level}-b-win2016 worker types in OCC, but for this bug, I think we're done, as we've shown generic-worker to run on Windows Server 2016. \o/
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Holy cow...thanks, Pete! Didn't expect it this quickly!
(In reply to Chris Cooper [:coop] from comment #5)
> Holy cow...thanks, Pete! Didn't expect it this quickly!

haha, you're welcome! :)

..... Just to be extra sure/safe, I also double checked it really had built on Windows 10 by running 'ver' on a worker (taskId Js9vk_dYSHapG_T01cS41A):

> Microsoft Windows [Version 10.0.14393]

So it is looking good. Feel free to play around with win2016 worker type. Note, it might not have everything on it required for gecko builds, but it should be usable for testing general task behaviour etc.

------------------------

[taskcluster 2017-09-19T16:06:44.316Z] Worker Type (win2016) settings:
[taskcluster 2017-09-19T16:06:44.316Z]   {
[taskcluster 2017-09-19T16:06:44.316Z]     "aws": {
[taskcluster 2017-09-19T16:06:44.316Z]       "ami-id": "ami-3c847944",
[taskcluster 2017-09-19T16:06:44.316Z]       "availability-zone": "us-west-2a",
[taskcluster 2017-09-19T16:06:44.316Z]       "instance-id": "i-049333b738dc298a9",
[taskcluster 2017-09-19T16:06:44.316Z]       "instance-type": "m3.2xlarge",
[taskcluster 2017-09-19T16:06:44.316Z]       "local-ipv4": "172.31.40.95",
[taskcluster 2017-09-19T16:06:44.316Z]       "public-hostname": "ec2-34-209-54-148.us-west-2.compute.amazonaws.com",
[taskcluster 2017-09-19T16:06:44.317Z]       "public-ipv4": "34.209.54.148"
[taskcluster 2017-09-19T16:06:44.317Z]     },
[taskcluster 2017-09-19T16:06:44.317Z]     "config": {
[taskcluster 2017-09-19T16:06:44.317Z]       "deploymentId": "Y98j1sWYSb2Z9auiFRhvpQ",
[taskcluster 2017-09-19T16:06:44.317Z]       "runTasksAsCurrentUser": false
[taskcluster 2017-09-19T16:06:44.317Z]     },
[taskcluster 2017-09-19T16:06:44.317Z]     "generic-worker": {
[taskcluster 2017-09-19T16:06:44.317Z]       "go-arch": "amd64",
[taskcluster 2017-09-19T16:06:44.317Z]       "go-os": "windows",
[taskcluster 2017-09-19T16:06:44.317Z]       "go-version": "go1.8.3",
[taskcluster 2017-09-19T16:06:44.317Z]       "release": "https://github.com/taskcluster/generic-worker/releases/tag/v10.2.2",
[taskcluster 2017-09-19T16:06:44.317Z]       "version": "10.2.2"
[taskcluster 2017-09-19T16:06:44.317Z]     },
[taskcluster 2017-09-19T16:06:44.317Z]     "machine-setup": {
[taskcluster 2017-09-19T16:06:44.317Z]       "maintainer": "pmoore@mozilla.com",
[taskcluster 2017-09-19T16:06:44.317Z]       "script": "https://raw.githubusercontent.com/taskcluster/generic-worker/master/worker_types/win2016/userdata"
[taskcluster 2017-09-19T16:06:44.317Z]     }
[taskcluster 2017-09-19T16:06:44.317Z]   }
[taskcluster 2017-09-19T16:06:44.317Z] Task ID: Js9vk_dYSHapG_T01cS41A
[taskcluster 2017-09-19T16:06:44.317Z] === Task Starting ===
[taskcluster 2017-09-19T16:06:51.234Z] Uploading redirect artifact public/logs/live.log to URL https://elitnfaaaaav5gxi3fkxndrfdckzoiaasste2kgxbmpzgu5w.taskcluster-worker.net:60023/log/B4vjYEc-S76tPfHkP0CAaQ with mime type "text/plain; charset=utf-8" and expiry 2017-09-19T16:11:44.853Z
[taskcluster 2017-09-19T16:06:51.754Z] Executing command 0: ver

C:\Users\task_1505837103>ver

Microsoft Windows [Version 10.0.14393]
[taskcluster 2017-09-19T16:06:51.863Z]    Exit Code: 0
[taskcluster 2017-09-19T16:06:51.863Z] Success Code: 0x0
[taskcluster 2017-09-19T16:06:51.864Z]    User Time: 0s
[taskcluster 2017-09-19T16:06:51.864Z]  Kernel Time: 15.625ms
[taskcluster 2017-09-19T16:06:51.864Z]    Wall Time: 86.9344ms
[taskcluster 2017-09-19T16:06:51.864Z]  Peak Memory: 4915200
[taskcluster 2017-09-19T16:06:51.864Z]       Result: SUCCEEDED
[taskcluster 2017-09-19T16:06:51.864Z] === Task Finished ===
[taskcluster 2017-09-19T16:06:51.864Z] Task Duration: 110.374ms
[taskcluster 2017-09-19T16:06:52.549Z] Uploading redirect artifact public/logs/live.log to URL https://queue.taskcluster.net/v1/task/Js9vk_dYSHapG_T01cS41A/runs/0/artifacts/public/logs/live_backing.log with mime type "text/plain; charset=utf-8" and expiry 2019-09-20T16:01:06.461Z
Just spotted Windows Server 2016 and Windows 10 share version number, so here is more useful output:


C:\Users\task_1505837160>systeminfo

Host Name:                 EC2AMAZ-1798TUD
OS Name:                   Microsoft Windows Server 2016 Datacenter
OS Version:                10.0.14393 N/A Build 14393
OS Manufacturer:           Microsoft Corporation
OS Configuration:          Standalone Server
OS Build Type:             Multiprocessor Free
Registered Owner:          EC2
Registered Organization:   Amazon.com
Product ID:                00376-40000-00000-AA273
Original Install Date:     9/19/2017, 7:57:52 AM
System Boot Time:          9/19/2017, 4:07:16 PM
System Manufacturer:       Xen
System Model:              HVM domU
System Type:               x64-based PC
Processor(s):              1 Processor(s) Installed.
                           [01]: Intel64 Family 6 Model 62 Stepping 4 GenuineIntel ~2500 Mhz
BIOS Version:              Xen 4.2.amazon, 8/24/2006
Windows Directory:         C:\Windows
System Directory:          C:\Windows\system32
Boot Device:               \Device\HarddiskVolume1
System Locale:             en-us;English (United States)
Input Locale:              en-us;English (United States)
Time Zone:                 (UTC) Coordinated Universal Time
Total Physical Memory:     30,720 MB
Available Physical Memory: 29,468 MB
Virtual Memory: Max Size:  35,584 MB
Virtual Memory: Available: 34,432 MB
Virtual Memory: In Use:    1,152 MB
Page File Location(s):     C:\pagefile.sys
Domain:                    WORKGROUP
Logon Server:              \\EC2AMAZ-1798TUD
Hotfix(s):                 9 Hotfix(s) Installed.
                           [01]: KB3176936
                           [02]: KB3186568
                           [03]: KB3192137
                           [04]: KB3199209
                           [05]: KB3199986
                           [06]: KB4013418
                           [07]: KB4023834
                           [08]: KB4035631
                           [09]: KB4034658
Network Card(s):           1 NIC(s) Installed.
                           [01]: AWS PV Network Device
                                 Connection Name: Ethernet 2
                                 DHCP Enabled:    Yes
                                 DHCP Server:     172.31.32.1
                                 IP address(es)
                                 [01]: 172.31.46.178
                                 [02]: fe80::58e5:5d4b:5fb9:fc08
Hyper-V Requirements:      A hypervisor has been detected. Features required for Hyper-V will not be displayed.


This is the output of "systeminfo" command in https://public-artifacts.taskcluster.net/Vn09HkF4R6WAvpWwqMZEeA/0/public/logs/live_backing.log which shows this really is Windows Server 2016, and not Windows 10. :-)
Component: Generic-Worker → Workers
You need to log in before you can comment on or make changes to this bug.