Closed Bug 859524 Opened 12 years ago Closed 12 years ago

Add buildbot-master5{5..8} to DNS

Categories

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

Product:
Infrastructure & Operations
Component:
RelOps: General
Platform:
x86_64
Linux
Type:
task
Priority:
Not set
Severity:
major

Tracking

(Not tracked)

Status:
VERIFIED FIXED

People

(Reporter: rail, Assigned: arich)

References

Details

+++ This bug was initially created as a clone of Bug #855740 +++ Please add the following AWS master to DNS: 10.134.49.93 -> buildbot-master55.srv.releng.use1.mozilla.com 10.132.50.142 -> buildbot-master56.srv.releng.usw2.mozilla.com 10.134.48.228 -> buildbot-master57.srv.releng.use1.mozilla.com 10.132.49.125 -> buildbot-master58.srv.releng.usw2.mozilla.com Inventory is up to date. Marking as major because of the upcoming b2g workweek. TYIA!
DNS added. Please remember that this component does not page anyone based on bug priority. If you need assistance immediately, please file the bug in the server ops area where the oncall SRE will see it. They can add DNS entries as easily as relops.
Assignee: server-ops-releng → arich
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Paging would be an overkill for "major" in any case. Thanks a lot!
Status: RESOLVED → VERIFIED
Rail: "major" does page in the ops queue (that's what the priorities above normal are for). :D
Uh, oh. I thought that only critical/blocker pages.
Component: Server Operations: RelEng → RelOps
Product: mozilla.org → Infrastructure & Operations
You need to log in before you can comment on or make changes to this bug.