Closed
Bug 1135849
Opened 10 years ago
Closed 10 years ago
Configure PULSE_URI/PULSE_EXCHANGE_NAMESPACE config in staging.
Categories
(Tree Management :: Treeherder: Infrastructure, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: jlal, Assigned: jlal)
References
Details
Bug 1113281 introduced a new config replacing PULSE_USERNAME and PULSE_PASSWORD (now is one config PULSE_URI) the new config should be set to something like this:
PULSE_URI = 'amqps://{PULSE_USERNAME}:{PULSE_PASSWORD}@pulse.mozilla.org:5671'
The PULSE_USERNAME and PULSE_PASSWORD configs should already be present on both stage an prod (if not I can supply you with new configs)
Assignee | ||
Comment 1•10 years ago
|
||
@fubar - Let me know when you have time to do the puppet reconfig (on stage first ideally) and I can test out the result to make sure everything looks good. Thanks!
Flags: needinfo?(klibby)
Comment 2•10 years ago
|
||
Added PULSE_URL to staging in r101049. Manually ran puppet, synced local.py and restarted services. Shout if there's an issue!
Also, as I said in IRC, we don't have credentials for prod atm.
Flags: needinfo?(klibby)
Assignee | ||
Comment 3•10 years ago
|
||
Looks like we need one more config here :
PULSE_EXCHANGE_NAMESPACE = PULSE_USERNAME
Comment 4•10 years ago
|
||
Added!
Assignee | ||
Comment 5•10 years ago
|
||
This bit is fixed but exposes another bug (1135924)
Assignee | ||
Updated•10 years ago
|
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Summary: Configure PULSE_URI config in staging / production. → Configure PULSE_URI/PULSE_EXCHANGE_NAMESPACE config in staging.
Updated•10 years ago
|
Assignee: nobody → jlal
You need to log in
before you can comment on or make changes to this bug.
Description
•