generic_worker puts hosts directly into service

RESOLVED FIXED

Status

RESOLVED FIXED
a year ago
a year ago

People

(Reporter: dividehex, Assigned: dividehex)

Tracking

Details

Attachments

(1 attachment, 1 obsolete attachment)

(Assignee)

Description

a year ago
Created attachment 8875370 [details] [diff] [review]
disable generic worker on mdc mac minis

Including generic_worker module puts hosts directly into service within taskcluster.  There is currently no other gate check to prevent that.

This means all the mac minis that got imaged in mdc1 a couple weeks ago are running tier 2 jobs and need to be disabled.
Attachment #8875370 - Flags: review?(wcosta)
Attachment #8875370 - Flags: review?(wcosta) → review+
(Assignee)

Comment 1

a year ago
That patch is not going to work since it is an agent and not a daemon service in the eyes of launchd.  And I can't figure out how to even unload the agent from the cli.  Using an exec to pkill it will only cause launchd to relaunch it.  So this might mean rm -rf the plist and reboot. :-(
(Assignee)

Comment 2

a year ago
Created attachment 8875474 [details] [diff] [review]
disable generic worker on mdc mac minis

Falling back to removing the plist.  We'll reboot the hosts manually with ansible or something to that effect.
Attachment #8875370 - Attachment is obsolete: true
Attachment #8875474 - Flags: review?(wcosta)
Attachment #8875474 - Flags: review?(wcosta) → review+
(Assignee)

Updated

a year ago
Attachment #8875474 - Flags: checked-in+
(Assignee)

Comment 3

a year ago
These never got rebooted so they were still taking jobs. Mea cupla.

I've since mass rebooted all the testers in mdc1.  A few spot checks shows the worker daemon is no longer starting at boot.
Status: NEW → RESOLVED
Last Resolved: a year ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.