Closed
Bug 564175
Opened 16 years ago
Closed 16 years ago
talos-r3-fed-037 needs setting up
Categories
(Release Engineering :: General, defect, P2)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: catlee, Assigned: bhearsum)
Details
(Whiteboard: [talos])
Looks like it's been freshly cloned. It's not running buildbot in any case.
| Reporter | ||
Comment 1•16 years ago
|
||
talos-r3-fed-033 too
| Assignee | ||
Comment 2•16 years ago
|
||
This is probably Puppet related, I'll have a quick look.
Assignee: nobody → bhearsum
| Assignee | ||
Comment 3•16 years ago
|
||
These slaves never had their hostnames changed post-clone. They were reporting into Puppet as the ref machine, and the buildbot-tac generator refused to generate anything because of the hostname. I changed the hostnames on both of these and ran:
puppetca --clean talos-r3-fed-037.build.mozilla.org
puppetca --clean talos-r3-fed-033.build.mozilla.org
on production-puppet to clean out the old certs.
They both connected to talos-master:9012 afterwards.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
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
•