Closed
Bug 579623
Opened 14 years ago
Closed 14 years ago
Graph server doesn't believe that talos-r3-leopard-051 exists
Categories
(Release Engineering :: General, defect, P2)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: khuey, Assigned: nthomas)
References
()
Details
FAIL: Failed to send data 5 times... quitting RETURN:send failed, graph server says: RETURN:No machine_name called 'talos-r3-leopard-051' can be found RETURN: File "/data/www/graphs.mozilla.org/server/pyfomatic/collect.py", line 255, in handleRequest RETURN: metadata = MetaDataFromTalos(databaseCursor, databaseModule, inputStream) RETURN: File "/data/www/graphs.mozilla.org/server/pyfomatic/collect.py", line 59, in __init__ RETURN: self.doDatabaseThings(databaseCursor) RETURN: File "/data/www/graphs.mozilla.org/server/pyfomatic/collect.py", line 88, in doDatabaseThings RETURN: raise DatabaseException("No machine_name called '%s' can be found" % self.machine_name)
Assignee | ||
Comment 1•14 years ago
|
||
This is a machine that should not be in production yet. I'll pull it and any pals that also snuck under the wire.
Assignee: nobody → nrthomas
Priority: -- → P2
Assignee | ||
Comment 2•14 years ago
|
||
Disconnected talos-r3-leopard-051 and talos-r3-fed-051/052/053. The Fedora boxes were connected to the wrong master and would not have received any work. The hostname of the master was modified in the snow leopard, leopard, fedora and xp boxes to ensure they don't connect to the master. The fed64 and w7 boxes don't have the correct hostnames set, so there is no buildbot tac or it has a bogus slavename.
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
•