Closed
Bug 551622
Opened 14 years ago
Closed 14 years ago
win32-slave38 has production keys
Categories
(Release Engineering :: General, defect, P5)
Release Engineering
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: mozilla, Unassigned)
Details
We sometimes have production keys in staging, which is possibly a bug in itself. I wondered in bug 532925 comment 26 why we don't add the production keys to the appropriate staging authorized_keys areas -- we'd still have the wrong keys in staging but we wouldn't find out during a failed upload or whatever. Filing in case other people agree. Or to publicly mark my shame when it's WONTFIXed.
Comment 1•14 years ago
|
||
My only worry here is that we somehow end up with a staging slave that has production keys, don't notice, and then it somehow uploads something bad to production systems. Is it that big of a burden to swap the keys when bringing it back?
Reporter | ||
Comment 2•14 years ago
|
||
Ok. Morphing bug.
Summary: add production keys to staging-stage authorized_keys → win32-slave38 has production keys
Reporter | ||
Comment 3•14 years ago
|
||
And resolving, unless opsi is managing keys.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Assignee | ||
Updated•11 years ago
|
Product: mozilla.org → Release Engineering
You need to log in
before you can comment on or make changes to this bug.
Description
•