Kedar Vaijanapurkar from Pythian cannot connect to subversion: $ ssh-add /h01/home/vaijanapurkar/.ssh/id_moz Enter passphrase for /h01/home/vaijanapurkar/.ssh/id_moz: Identity added: /h01/home/vaijanapurkar/.ssh/id_moz (/h01/home/vaijanapurkar/.ssh/id_moz) $ svn co svn+ssh://svn.mozilla.org/sysadmins/puppet/trunk/manifests/nodes/db_mysql Could not chdir to home directory : No such file or directory You do not have a valid subversion account here! 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 $ Access was set up in bug 1241722. I thought all that was needed was to put him in the vpn_pythian_dba LDAP group? Not sure if he's in there. This access is needed for tomorrow's TCW.
So svn is *not* enabled nor sysadmin svn there. I'll need a quick hack from cshields for that I think.
No hack needed - this is something in place for the rest of the Pythian contractors, like email@example.com and firstname.lastname@example.org. They have permissions to check out/edit/check in: sysadmins/puppet/trunk/manifests/nodes/db_mysql and sysadmins/puppet/trunk/modules/mysql2 So, there's already something in place, I'm not sure what. I thought the VPN group covered the svn there.
See also: https://bugzilla.mozilla.org/show_bug.cgi?id=1158950#c26 Not sure if it's digi, or atoll, or fubar, but there's reference to authz....maybe it's sysadmins/puppet/trunk/modules/svn/files/svn/sysadmins/authz ???
(In reply to Sheeri Cabral [:sheeri] from comment #3) > See also: https://bugzilla.mozilla.org/show_bug.cgi?id=1158950#c26 > > Not sure if it's digi, or atoll, or fubar, but there's reference to > authz....maybe it's > > sysadmins/puppet/trunk/modules/svn/files/svn/sysadmins/authz ??? yep and svn needs to be enabled. I'll look at beebe and copy what he has.
added cn=svn_sysadmins,ou=groups,dc=mozilla added email@example.com to the pythian group in Authz, in 118176.
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → FIXED
Verified, thank you! Ludo - So when there's a new Pythian consultant, what do we have to do besides request they be put in the vpn_pythian_dba LDAP group?
Status: RESOLVED → VERIFIED
(In reply to Sheeri Cabral [:sheeri] from comment #6) > Verified, thank you! > > Ludo - So when there's a new Pythian consultant, what do we have to do > besides request they be put in the vpn_pythian_dba LDAP group? comment 5 says it all.
Ah, OK, thanx. Will update our docs.
You need to log in before you can comment on or make changes to this bug.