Closed
Bug 751707
Opened 12 years ago
Closed 12 years ago
replace buildbot and buildbot_reader usernames/passwords globally
Categories
(Release Engineering :: General, defect)
Release Engineering
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: dustin, Assigned: nthomas)
Details
Per bug 751605, we'll need to replace these usernames/passwords with new credentials. I've GPG'd these to bear, and he can spread them around as needed.
Assignee | ||
Updated•12 years ago
|
Assignee: nobody → nrthomas
Assignee | ||
Comment 1•12 years ago
|
||
I've updated secrets.pp on master-puppet1, specifically buildbot_schedulerdb_user buildbot_schedulerdb_password buildbot_statusdb_user buildbot_statusdb_password buildapi_schedulerdb_user buildapi_schedulerdb_password buildapi_schedulerdb_rwuser buildapi_schedulerdb_rwpassword buildapi_statusdb_user buildapi_statusdb_password
Assignee | ||
Comment 2•12 years ago
|
||
Rail reports the masters are all done, and I have buildapi up again. Just need to do the right thing for the scheduler move to bm36.
Assignee | ||
Comment 3•12 years ago
|
||
I think that's everything in prod except for maybe autoland. lsblakk, do you use the buildbot_reader user when talking to the buildbot_schedulers db ?
Comment 4•12 years ago
|
||
We do use buildbot_reader for schedulerdbpoller (in autoland) - will need these updated passwords please.
Assignee | ||
Comment 5•12 years ago
|
||
After speak to Lukas, she's going to take care of autoland-staging02 (current production). Dustin, can you take care of the new dev/staging/prod systems ?
Reporter | ||
Comment 6•12 years ago
|
||
It's arguable which are "production" :) I updated the password on the production autoland cluster and pushed.
Reporter | ||
Comment 7•12 years ago
|
||
Are we done here? Can we delete the old usernames?
Comment 8•12 years ago
|
||
need to hear back that autoland has changed
Reporter | ||
Comment 9•12 years ago
|
||
autoland-staging* are fixed, per lukas
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
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
•