If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Grant talos tiger machines access to http://build.mozilla.org/talos w/o LDAP auth

RESOLVED FIXED

Status

mozilla.org Graveyard
Server Operations
--
major
RESOLVED FIXED
7 years ago
3 years ago

People

(Reporter: armenzg, Assigned: fox2mike)

Tracking

Details

(Reporter)

Description

7 years ago
This bug is almost like bug 568678 but for the tiger slaves that were not moved to the build network.

I believe this is just a modification in a firewall rule.

The machines trying to reach that page are:
* talos-rev2-tiger{01,14}.mozilla.org

This is important to get done soon since it is currently keeping the talos runs for these machines red.
(Reporter)

Updated

7 years ago
Blocks: 571565
(Reporter)

Updated

7 years ago
No longer blocks: 571565
(Reporter)

Updated

7 years ago
Blocks: 571565
Armen means a range of 01 thru to 14 there, rather than two machines.
(Reporter)

Comment 2

7 years ago
right; '-' (dash) rather than ','
(Assignee)

Comment 3

7 years ago
Okay, so this isn't a firewall issue, because these machines can already connect to build.m.o

Poking at the apache config.
Assignee: server-ops → shyam
(Assignee)

Comment 4

7 years ago
Added an Allow line for 10.2.73 in the apache config. Although this means any of the QA machines can hit /talos without auth, I don't really expect anyone to "abuse" this and it's a pain to add Allow lines for 14 machines...

So this should be fixed.
Status: NEW → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → FIXED
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.