Closed Bug 993728 Opened 8 years ago Closed 8 years ago

Deploy .boto configuration for Windows build slaves (GPO)

Categories

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

task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: mshal, Assigned: q)

References

Details

Similar to bug 987537, we'd like to deploy the .boto config file (which contains keys for ceph) on Windows build slaves. The file should be c:\users\cltbld\.boto - is GPO well-suited for files that contain secrets like this? It should be removed from the machine when it is loaned out, and added back in when the machine is put back into production.
Hi, mshai, what's the urgency on this?  We've got a bunch of high priority things on our plate this week.
I'm not sure where this ranks priority-wise. Maybe taras knows?
Flags: needinfo?(taras.mozilla)
(In reply to Michael Shal [:mshal] from comment #2)
> I'm not sure where this ranks priority-wise. Maybe taras knows?

high
Flags: needinfo?(taras.mozilla)
where high is > seamicro project
Assignee: relops → q
Looks like the deployment of these files to cltbld's %USERPROFILE% directory is going smoothly for builders. these are set to be deleted if the machine is moved to the loaner state.
all deployed and future machines will also receive.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Somehow some slaves have an empty .boto file instead of what's supposed to be there.
At least w64-ix-slave45, 57, 59, 68 and 162.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
I believe this was all resolved.
Status: REOPENED → RESOLVED
Closed: 8 years ago8 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.