Closed
Bug 566877
Opened 14 years ago
Closed 14 years ago
win32 try slaves in build network can't reach build.mozilla.org to upload symbols
Categories
(mozilla.org Graveyard :: Server Operations, task)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: lsblakk, Assigned: dmoore)
References
Details
newly re-imaged and moved out of sandbox slaves: try-w32-slave{12,13,14,16,17,18,19}.build are not reaching build.mozilla.org to upload symbols - firewall?
Reporter | ||
Updated•14 years ago
|
Summary: win32 try slaves in build network can't upload symbols to build.mozilla.org → win32 try slaves in build network can't reach build.mozilla.org to upload symbols
Assignee | ||
Updated•14 years ago
|
Assignee: server-ops → dmoore
Assignee | ||
Comment 1•14 years ago
|
||
Upload in what way? We currently allow HTTPS and SSH access, which is same as what was granted to the sandbox slaves. The firewall hasn't logged any blocked connections, so I'm wondering what else might be happening on the slave side.
Comment 2•14 years ago
|
||
Does the *.build.mozilla.org and build.mozilla.org unfortunate naming collision hurt anything? (/me has been wondering this for a while)
Reporter | ||
Comment 3•14 years ago
|
||
They are trying to upload to build.mozilla.org as trybld with SSH - I just went on and did it manually and it just needed acceptance for known host. Will do that on all the new slaves. Sorry for the panic.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Updated•9 years ago
|
Product: mozilla.org → mozilla.org Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•