1300135 - generic-worker not starting on gecko-1-t-win7-32 workertypes

Status: RESOLVED FIXED

(Taskcluster :: Workers, defect)

Description

[Rob Thijssen [:grenade (EET/UTC+0300)]]

After the fact bug to track resolution. So far:
- pmoore updated g-w to provide more verbose logging (https://github.com/taskcluster/generic-worker/commit/e1b013b94038e0bef622df72c44b0afbb0f35db5)
- grenade updated occ to remove aotologin keys before g-w install run (https://github.com/mozilla-releng/OpenCloudConfig/commit/92217af7d9f08086c6a88889e6c95c40a8ed4d24)

Comment 1

[Rob Thijssen [:grenade (EET/UTC+0300)]]

after testing with the debug logging, there's a couple issues:
- if the autologon reg keys pre-exist, the g-w install fails. i've worked around this by deleting the keys at the start of ami generation
- if the start-g-w-at-logon scheduled task pre-exists, the g-w install fails. i tried to work around this by deleting the task but on win7 dsc runs under the system account which doesn't seem able to succeed at that. we'll need to put some logic into g-w to overwrite the task instead if it pre-exists.

:pmoore, do you think this is feasible to add to g-w?

Comment 2

[Pete Moore [:pmoore][:pete]]

In short, yes, I can do that. =)

However, let's also create a bug to create clean win7 images, even if we don't plan it for this quarter (Q3 2016).

I'll try to make the generic worker installation idempotent, as much as I can.

Comment 3

[Rob Thijssen [:grenade (EET/UTC+0300)]]

we worked around this by cleaning up after old g-w installs in userdata. g-w itself is unchanged.