Closed
Bug 815137
Opened 12 years ago
Closed 12 years ago
allow partner-repack1 to generate signing tokens
Categories
(Release Engineering :: General, defect)
Release Engineering
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: bhearsum, Unassigned)
References
Details
Can't do this until we know what its IP address will be inside of the build network.
Reporter | ||
Updated•12 years ago
|
Summary: allow dm-partnerdist01 to generate signing tokens → allow partner-repack1 to generate signing tokens
Reporter | ||
Comment 1•12 years ago
|
||
To do next week: add 10.26.48.41 (partner-repack1s.rv.releng.scl3.mozilla.com) to the list of machines allowed to generate a signing token.
Reporter | ||
Comment 2•12 years ago
|
||
I added 10.26.48.41 to the list of masterIPs in secrets.pp on master-puppet1. They signing servers should reload themselves for this shortly.
Reporter | ||
Comment 3•12 years ago
|
||
Did a few spotchecks and it looks like everything has picked this up.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Assignee | ||
Updated•12 years ago
|
Product: mozilla.org → Release Engineering
Assignee | ||
Updated•7 years ago
|
Component: General Automation → General
You need to log in
before you can comment on or make changes to this bug.
Description
•