Closed Bug 1338560 Opened 8 years ago Closed 8 years ago

VPN access for pmoore to t-yosemite-r7-{0040..0049}

Categories

(Infrastructure & Operations Graveyard :: CIDuty, task)

task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: pmoore, Assigned: aselagea)

References

Details

Thanks Alin! Let me know if you need more information.
Granted VPN access for t-yosemite-r7 machines in range [0040-0059]. Let me know if everything works fine.
Yay, worked perfectly, thanks Alin! :-) \o/
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Hi Alin, I seem to have lost access somehow :/ - any ideas what might have caused this? pmoore@Petes-iMac:~/git/puppet master $ ssh -v pmoore@t-yosemite-r7-0041.test.releng.scl3.mozilla.com OpenSSH_6.9p1, LibreSSL 2.1.8 debug1: Reading configuration data /Users/pmoore/.ssh/config debug1: /Users/pmoore/.ssh/config line 40: Applying options for *.mozilla.com debug1: Reading configuration data /etc/ssh/ssh_config debug1: /etc/ssh/ssh_config line 21: Applying options for * debug1: /etc/ssh/ssh_config line 55: Applying options for * debug1: Connecting to t-yosemite-r7-0041.test.releng.scl3.mozilla.com [10.26.57.216] port 22. debug1: Connection established. debug1: identity file /Users/pmoore/.ssh/id_rsa type 1 debug1: key_load_public: No such file or directory debug1: identity file /Users/pmoore/.ssh/id_rsa-cert type -1 debug1: key_load_public: No such file or directory debug1: identity file /Users/pmoore/.ssh/id_dsa type -1 debug1: key_load_public: No such file or directory debug1: identity file /Users/pmoore/.ssh/id_dsa-cert type -1 debug1: key_load_public: No such file or directory debug1: identity file /Users/pmoore/.ssh/id_ecdsa type -1 debug1: key_load_public: No such file or directory debug1: identity file /Users/pmoore/.ssh/id_ecdsa-cert type -1 debug1: key_load_public: No such file or directory debug1: identity file /Users/pmoore/.ssh/id_ed25519 type -1 debug1: key_load_public: No such file or directory debug1: identity file /Users/pmoore/.ssh/id_ed25519-cert type -1 debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_6.9 debug1: Remote protocol version 2.0, remote software version OpenSSH_6.2 debug1: match: OpenSSH_6.2 pat OpenSSH* compat 0x04000000 debug1: Authenticating to t-yosemite-r7-0041.test.releng.scl3.mozilla.com:22 as 'pmoore' debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: server->client aes128-ctr umac-64-etm@openssh.com zlib@openssh.com debug1: kex: client->server aes128-ctr umac-64-etm@openssh.com zlib@openssh.com debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<3072<8192) sent debug1: got SSH2_MSG_KEX_DH_GEX_GROUP debug1: SSH2_MSG_KEX_DH_GEX_INIT sent debug1: got SSH2_MSG_KEX_DH_GEX_REPLY debug1: Server host key: ssh-rsa SHA256:nPT1bVRyic8L8MLh4Hsi74l3xfZ6rwHo+lVfXLmKJ8s debug1: Host 't-yosemite-r7-0041.test.releng.scl3.mozilla.com' is known and matches the RSA host key. debug1: Found key in /Users/pmoore/.ssh/known_hosts:215 debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug1: SSH2_MSG_NEWKEYS received debug1: SSH2_MSG_SERVICE_REQUEST sent debug1: SSH2_MSG_SERVICE_ACCEPT received debug1: Authentications that can continue: publickey,password debug1: Next authentication method: publickey debug1: Offering RSA public key: /Users/pmoore/.ssh/id_rsa debug1: Authentications that can continue: publickey,password debug1: Trying private key: /Users/pmoore/.ssh/id_dsa debug1: Trying private key: /Users/pmoore/.ssh/id_ecdsa debug1: Trying private key: /Users/pmoore/.ssh/id_ed25519 debug1: Next authentication method: password pmoore@t-yosemite-r7-0041.test.releng.scl3.mozilla.com's password: I get the same on all 10 of these machines (t-yosemite-r7-004[0-9].test.releng.scl3.mozilla.com)
Status: RESOLVED → REOPENED
Flags: needinfo?(aselagea)
Resolution: FIXED → ---
Summary: VPN access for pmoore to t-yosemite-r7-{0040..0059} → VPN access for pmoore to t-yosemite-r7-{0040..0049}
The log above shows you were using your user ('pmoore') to connect to the machine (which does not exist). :) Connecting as 'root' or 'cltbld' should work fine.
Status: REOPENED → RESOLVED
Closed: 8 years ago8 years ago
Flags: needinfo?(aselagea)
Resolution: --- → FIXED
I'm such an idiot. Thanks Alin!
Component: Loan Requests → Buildduty
Product: Release Engineering → Infrastructure & Operations
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.