Closed Bug 545567 Opened 11 years ago Closed 11 years ago

Allow some of 10.250.48 to reach build.m.o

Categories

(mozilla.org Graveyard :: Server Operations, task)

x86
All
task
Not set
major

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: nthomas, Assigned: dmoore)

References

Details

We have some machines in 10.250.48 that need to talk to build.m.o:/var/www/html/build/clobberer and stage-clobberer. We would like to update the Allow list in the apache config to achieve that. I know at least that 10.250.48.206 thru 212 will be needed, but have lost track of other build.m.o machines that might be in that address space.
Correction, we need 10.250.48.206 thru 214 at least. Please check for any more you can find in that block belonging to us and we'll let you know if they need access.

[ Background for RelEng - 206 thru 214 is moz2-darwin9-slave29 thru 37 (from 
[ bug 528281). They were failing to build tracemonkey due to a merge from 
[ mozilla-central, which sayrer set a clobber to resolve. That wasn't being 
[ picked that up:
[  Checking clobber URL: http://build.mozilla.org/clobberer/index.php...
[  Error contacting server
[  program finished with exit code 1
Severity: normal → major
[ Manually clobbered those machines for now ]
Assignee: server-ops → dmoore
Blocks: 545136
This also affects the new ix machines too, those currently up are bug 545134 comment 9. Perhaps we should just add the whole subnet to build.m.o:/etc/httpd/conf/domains/build.mozilla.org.conf
We're going to go ahead with the full subnet inclusion, per Nick in Comment #3
Can this get done today? I'm hoping to put some machines in production on Monday morning.
MV build subnet granted access to clobberer and stage-clobberer
Status: NEW → RESOLVED
Closed: 11 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.