Closed
Bug 629006
Opened 15 years ago
Closed 15 years ago
set up talos-r3-fed64-040 after re-image
Categories
(Release Engineering :: General, defect, P3)
Release Engineering
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: dustin, Unassigned)
References
Details
(Whiteboard: [slaveduty])
once it's re-imaged, that is
|
||
Updated•15 years ago
|
Whiteboard: [slaveduty]
|
||
Updated•15 years ago
|
Priority: -- → P3
|
||
Comment 1•15 years ago
|
||
I noticed something funny about this last week:
$ ssh cltbld@talos-r3-fed64-030.build.mozilla.org 'hostname; grep ^slavename talos-slave/buildbot.tac'
talos-r3-fed64-040.build.mozilla.org
slavename = 'talos-r3-fed64-040'
So 030 thinks it is 040. Can't raise 040 with ssh or VNC, but nagios thinks it is up. DNS for 030 and 040 is unique and consistent with itself.
|
Reporter | |
Comment 2•15 years ago
|
||
comment 1 branched to bug 626020.
The box in this bug - talos-r3-fed-040 - is currently unpingable as reported on the currrent reboots bug.
Depends on: 635416
|
|
||
Comment 3•15 years ago
|
||
Summary currently says -fed64-040.
|
|
Reporter | |
Comment 4•15 years ago
|
||
Right, I mistyped in comment 2. That should indicate that "talos-r3-fed64-040" is unpingable. Thanks for spotting it.
|
|
Reporter | |
Updated•15 years ago
|
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
|
Assignee | |
Updated•12 years ago
|
Product: mozilla.org → Release Engineering
You need to log in
before you can comment on or make changes to this bug.
Description
•