https://bugzilla.mozilla.org/show_bug.cgi?id=1082535#c80 means we're running some GPO tasks not at boot time. A client will check with the server periodically for updates, and as well as at boot. When it checks for the update, and it picks up a task such as a file copy it will begin executing the task. Other task such a package install, a security change, registry change, and others will not take effect or start until the next boot. Generally we don't want puppet or GPO services to run while machines are doing builds and/or tests. The possible slowdown could cause a machine to unexpectedly timeout during routine activity, and invoke a flurry of activity from sheriffs, buildduty, and devs as sheriffs back-out patches and close trees. However, Group Policy updates are all done through background processes, which should not affect foreground processes. We could disabled the refresh interval. The result would be Group Policy refreshes would occur on log in/ log out, or for our purposes during shutdown and after boot. We need to establish whether it is a problem or not that some changes can occur while buildbot jobs are ongoing. CC'ing Amy, Mark, Coop, Q to bring relevant stakeholders into the discussion. Thanks, Pete
Please note this issue derives originally from comments made in bug 1082535.
Dupe of bug 1086915 ?
(In reply to Nick Thomas [:nthomas] from comment #2) > Dupe of bug 1086915 ? Indeed! Thanks Nick.
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → DUPLICATE
Duplicate of bug: 1086915
Component: Platform Support → Buildduty
Product: Release Engineering → Infrastructure & Operations
You need to log in before you can comment on or make changes to this bug.