Closed Bug 648310 Opened 13 years ago Closed 13 years ago

put linux64-ix-slave37 into production-try

Categories

(Release Engineering :: General, defect, P4)

Product:
Release Engineering
Component:
General
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED WORKSFORME

People

(Reporter: dustin, Unassigned)

References

Details

(Whiteboard: [slaveduty][buildslaves]) 

More detail to follow.  It's only half setup as a new slave -- its hostname is wrong and its buildbot.tac is too.  But there may be other problems.
Assignee: nobody → jhford
Any update on the state of this machine?
(In reply to comment #1)
> Any update on the state of this machine?

No, I don't know what is wrong with this machine.  It is not in a known state and if i recall correctly, had networking issues for the majority of the time that I was setting up the linux64-ix slaves.  Unlike linux64-ix-slave35 (648312), I don't know of anything other than potential networking issues that would affect this slave.  We should finish the machine setup as normal, if there are no signs that this is a defective machine.
Assignee: jhford → nobody
OK, well, you're the one setting up such machines, so that's up to you.  I'll un-ack the nagios alerts for this system and leave the rest to you.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → INVALID
This machine was broken during the setup like many other machines.  I will be filing a bug momentarily to get this slave reimaged and back into try.
Status: RESOLVED → REOPENED
Resolution: INVALID → ---
Summary: linux64-ix-slave37 may be sick → put linux64-ix-slave37 into production-try
No longer blocks: 649449
Depends on: 649449
Priority: -- → P4
That box will be going to iX for repair, and it'll be allocated via slavealloc when it comes back, so nothing to do here.
Status: REOPENED → RESOLVED
Closed: 13 years ago → 13 years ago
Resolution: --- → WORKSFORME
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.