715002 - Can't access SVN on new host svn.allizom.org

Status: VERIFIED FIXED

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

Description

[hwine]

Per email from Amy, we should be able to checkout various puppet configs from the new svn server. However, the ssh connection times out prior to authenticating:

$ svn co svn+ssh://svn.allizom.org/sysadmins/puppet/trunk/modules/gitolite 
OpenSSH_5.6p1, OpenSSL 0.9.8r 8 Feb 2011
debug1: Reading configuration data /Users/Hal/.ssh/config
debug1: Applying options for svn.allizom.org
debug1: Reading configuration data /etc/ssh_config
debug1: Applying options for *
debug1: Connecting to svn.allizom.org [63.245.217.46] port 22.
svn: To better debug SSH connection problems, remove the -q option from 'ssh' in the [tunnels] section of your Subversion configuration file.
svn: Network connection closed unexpectedly

Both nthomas & jhford have experienced the same.

Comment 1

[Brian Hourigan [:digi]]

Thanks for reporting this. Can you let me know what machines you're connecting from? It's likely a flow issue and I will need this info for netops.

Comment 2

[Justin Dow [:jabba]]

If three relengers are having this issue, my first guess would be that it is because you are on the build vpn, which actively blocks pretty much everything not on a build vlan as I understand it. Can you try disconnecting from the build vpn and see if it works? If so, then we can turn this bug into a request for netops to allow that IP from the build VPN.

Comment 3

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

I get a public IP regardless of VPN state (63.245.217.46), and see the same lack of connection either way. Port 80 does responds. Perhaps we could flip it around and say that IT folks are getting a private IP and ssh works, but not on the public one ?

Comment 4

[Justin Dow [:jabba]]

Actually, yes you are correct, this is no longer working. I was testing this morning from the office and it worked and previously I'd tested from outside any vpns or network and it worked also. Now I'm getting the same error as you.. Doesn't work from outside the network at all...

CC'ing adam, who opened flows in https://bugzilla.mozilla.org/show_bug.cgi?id=710357

Comment 5

[Justin Dow [:jabba]]

This should work now. There was a regression during the zeus shuffles last week. Adam found and fixed the missing firewall rule. It should work from the public internet. If it doesn't work while on the build-vpn, that might be a separate issue.

Comment 6

[hwine]

Thanks - works for me from both sf office & build-vpn.

Comment 7

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

And for me with an extra permissions fix from digi.