Closed
Bug 617502
Opened 14 years ago
Closed 14 years ago
Some talos slaves still reporting to MV masters
Categories
(Release Engineering :: General, defect, P2)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: nthomas, Assigned: coop)
Details
(Whiteboard: [buildslaves][buildduty])
From the buildslaves list, which is admittedly not the last word since it's a snapshot in time, but I can't see any other slaves in statusdb in the last 36 hours either. I've verifed that DNS thinks all these slaves are in SCL. test-master01:8012 t-r3-w764-027 t-r3-w764-028 t-r3-w764-038 t-r3-w764-039 test-master02:8012 talos-r3-fed-011 talos-r3-fed-030 talos-master02:8012 is clean. These slaves may well be out of sync with puppet too, which is the main issue here. They're doing jobs OK.
Updated•14 years ago
|
Priority: P3 → --
Comment 1•14 years ago
|
||
In dealing with bug 616157 talos-r3-leopard-{049,050} came online attaching to talos-master02 initially, I've sent them over to buildbot-master2.build.scl1.mozilla.com:9012 now.
Comment 2•14 years ago
|
||
I've kicked talos-r3-fed-{011,030} over to buildbot-master2.build.scl1.mozilla.com as well. They do not appear to be having puppet problems.
Assignee | ||
Updated•14 years ago
|
Assignee: nobody → coop
Status: NEW → ASSIGNED
Priority: -- → P2
Assignee | ||
Comment 3•14 years ago
|
||
(In reply to comment #0) > t-r3-w764-027 > t-r3-w764-028 > t-r3-w764-038 > t-r3-w764-039 These are all reporting to buildbot-master2.build.scl1.mozilla.com now too.
Status: ASSIGNED → RESOLVED
Closed: 14 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
•