Closed Bug 564217 Opened 14 years ago Closed 14 years ago

Setup 30 new linux64 talos slaves

Categories

(Release Engineering :: General, defect, P2)

x86
All
defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: joduinn, Assigned: joduinn)

References

Details

(Whiteboard: [buildslaves][talos][unittest])

Attachments

(1 file)

This is to track: 

1) Add talos-r3-fed64-{021...050}.build.mozilla.org to staging and production master configs. They will all run in staging first, but we should keep 5 in staging. 

2) Add all to graphserver.
Please be sure to set the full hostnames on these by editing /etc/sysconfig/network.
Summary: Setup 30 new linux64 buildslaves → Setup 30 new linux64 talos slaves
All being worked on now, or very soon.
Priority: -- → P2
Whiteboard: [buildslaves][talos][unittest]
I can't reach 46 - 50
(In reply to comment #5)
> I can't reach 46 - 50

46-50 are powered on, and I can ssh into them just fine. However, the buildbot.tac is pointing to wrong master, so they are not picking up jobs, like the other 25 slaves. I'll fix this monday morning, and then close.
Assignee: nobody → joduinn
Blocks: 566333
These new slaves should have not been added to the pool before syncing up with puppet.

I have filed bug 566333 to keep track of the issue.
No longer blocks: 566333
Blocks: 566333
(In reply to comment #6)
> (In reply to comment #5)
> > I can't reach 46 - 50
> 
> 46-50 are powered on, and I can ssh into them just fine. However, the
> buildbot.tac is pointing to wrong master, so they are not picking up jobs, like
> the other 25 slaves. I'll fix this monday morning, and then close.

Now 46-50 are pointed to correct master, and accepting jobs. All done here.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Blocks: 566889
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.