596426 - tools staging environment needs access to build server

Status: RESOLVED FIXED

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

Description

[alice nodelman [:alice] [:anode]]

Can't currently download:


http://build.mozilla.org/talos/tools/buildfarm/utils/installdmg.sh
http://build.mozilla.org/talos/tools/buildfarm/maintenance/count_and_reboot.py
http://build.mozilla.org/talos/zips/talos.zip
http://build.mozilla.org/talos/xpis/pageloader.xpi


These need to be accessible from all
tools-r3-XXX-001/002.mv.mozilla.com

Making the whole talos directory + its sub-directories accessible would be preferable here.

Comment 1

[Joel Maher ( :jmaher ) (UTC -8)]

This is still a problem and I continue to run into it while trying to run staging on our talos/unittest staging setup.  What information can I provide to speed this up?

Comment 2

[Ravi Pina [:ravi]]

Every URL returns a HTTP/403 for me.  Is that what you are getting or are you not connecting to the server at all?

Comment 3

[Joel Maher ( :jmaher ) (UTC -8)]

I see this:
cltbld@localhost ~]$ wget http://build.mozilla.org/tools/zips/pagesets.zip
--07:24:22--  http://build.mozilla.org/tools/zips/pagesets.zip
Resolving build.mozilla.org... 10.2.74.128
Connecting to build.mozilla.org|10.2.74.128|:80... connected.
HTTP request sent, awaiting response... 302 Moved Temporarily
Location: https://build.mozilla.org/tools/zips/pagesets.zip [following]
--07:24:22--  https://build.mozilla.org/tools/zips/pagesets.zip
Connecting to build.mozilla.org|10.2.74.128|:443... connected.
HTTP request sent, awaiting response... 401 Authorization Required
Authorization failed.
[cltbld@localhost ~]$ 


Maybe Alice can clarify

Comment 4

[alice nodelman [:alice] [:anode]]

I am also getting 401 when attempting to pull a copy from the various tools slaves.

Comment 5

[Ravi Pina [:ravi]]

I'm unclear how this is an Ops issue let alone a network issue.  I think someone from Build may be better suited to handle this.

Comment 6

[Nick Thomas [:nthomas] (UTC+12)]

This is an Apache config issue on dm-wwwbuild01.m.o, which IT administers. Specifically the block beginning line 14 of /etc/httpd/conf/domains/build.mozilla.org.conf.
 
Alice, I can't resolve tools-r3-snow-001.mv.mozilla.com so I don't know what IPs you need added. There are lots of DNS changes going on so the FQDN may have changed recently. Please provide a full list of IPs you need to have access, and pass this back to mozilla.org::Server Ops.

Comment 7

[alice nodelman [:alice] [:anode]]

tools-staging-master.mv.mozilla.com has address 10.250.48.248
host tools-r3-fed-001 { hardware ethernet 34:15:9E:18:D7:52; fixed-address
10.250.1.182; }
host tools-r3-fed-002 { hardware ethernet 34:15:9E:18:4F:00; fixed-address
10.250.1.183; }
host tools-r3-fed64-001 { hardware ethernet 34:15:9E:18:65:F6; fixed-address
10.250.1.184; }
host tools-r3-fed64-002 { hardware ethernet 34:15:9E:18:60:CC; fixed-address
10.250.1.185; }
host tools-r3-w7-001 { hardware ethernet 34:15:9E:18:63:96; fixed-address
10.250.1.186; }
host tools-r3-w7-002 { hardware ethernet 34:15:9E:18:3A:C4; fixed-address
10.250.1.187; }
host tools-r3-xp-001 { hardware ethernet 34:15:9E:18:41:08; fixed-address
10.250.1.188; }
host tools-r3-xp-002 { hardware ethernet 34:15:9E:18:65:20; fixed-address
10.250.1.189; }
host tools-r3-leopard-001 { hardware ethernet 34:15:9E:18:3A:FE; fixed-address
10.250.1.190; }
host tools-r3-leopard-002 { hardware ethernet 34:15:9E:18:BD:48; fixed-address
10.250.1.191; }
host tools-r3-snow-001 { hardware ethernet 34:15:9E:18:62:24; fixed-address
10.250.1.192; }
host tools-r3-snow-002 { hardware ethernet 34:15:9E:18:D4:E2; fixed-address
10.250.1.193; }
host tools-r3-w764-001 { hardware ethernet 34:15:9E:18:3C:C0; fixed-address
10.250.1.194; }
host tools-r3-w764-002 { hardware ethernet 34:15:9E:18:D8:6C; fixed-address
10.250.1.195; }

Comment 8

[alice nodelman [:alice] [:anode]]

Passing back to server ops based upon comment #6.

Comment 9

[Justin Dow [:jabba]]

I added that IP block as an Allow directive.