Closed Bug 778942 Opened 14 years ago Closed 14 years ago

set resolution as builder user before buildbot starts

Categories

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

task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: dustin, Assigned: dustin)

References

Details

Attachments

(1 file)

Running 'screenresolution' doesn't work before anyone is logged in, which means that it won't work while puppetizing a new host. This *might* be able to work in puppet when it is not puppetizing, if we're lucky enough to run puppet after the autologin has completed. I'd prefer to run this as part of the buildbot startup process, though. At that point, we know the builder user is logged in, and we're running in the correct context.
Assignee: server-ops-releng → dustin
OK, well, this *does* seem to work as root, once the user is logged in, and puppet will retry if it cannot set the resolution because the automatic login has not proceeded. We only need to exclude this during puppetization, which is easy since there's a $::puppetizing fact. So, this will do for now, and if the timing turns out such that this fails, then we can revisit. We'll get error emails in that case.
Attached patch bug778942.patch — — Splinter Review
I named this screenresolution::talos in case we later want screenresolution::builder or screenresolution::maximum or something like that.
Attachment #647344 - Flags: review?(kmoir)
Attachment #647344 - Flags: review?(kmoir) → review+
Attachment #647344 - Flags: checked-in+
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Component: Server Operations: RelEng → RelOps
Product: mozilla.org → Infrastructure & Operations
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: