Project

General

Profile

Actions

Support #15986

closed

Requesting Lab Access

Added by Oleh Prypin almost 8 years ago. Updated almost 5 years ago.

Status:
Resolved
Priority:
Normal
Category:
User access
Target version:
-
% Done:

0%

Tags:
Reviewed:
Affected Versions:

Description

Hello, I am a student from GSoC.

I have been instructed to request access to Sepia to run jobs manually.

Username: oprypin (Oleh Prypin)

Public SSH key:

ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQCzf8fjotuelTIdz7clDpSN/VDtXirYrmzM/r157Np9uTMgn/rhzzplp2DKqFrCEDwawJ1O1Fr/H5DqttPonyRmjPmAIf96P8KKLsC600R63xk4DNhnByY0WBU3o1e46LP7DJLsOOy6hZRbyjgoFfzcapH7aV+fa37k7/Ri5mpmdmENa6lYI38+YaItFJf0kTXdFou0iLAt7xogOTimgblMst6UjOhRIsMFA3QS4PvOFR+AedCHeVtYK9mAeRtQ530wKzjz8x4NFU3Y93jmygwTTG2RTEfRjfbObfFOQXJGKcl28pxGPUL9ZlrLx1juAekn2Uz+2oO/eQ8G5w+XW3rp

Hashed VPN password:

oprypin@bx-pc-arch 5WYD7PWKwdSQjfGo95ehWw f3c9f170d74c6c443cf0f82f0d87045e1d3a0dbcd01474f6e667ea20a00978b3

Actions #1

Updated by David Galloway almost 8 years ago

  • Status changed from New to In Progress
  • Assignee set to David Galloway

jdurgin confirmed Tracker account e-mail address is valid via IRC.

https://github.com/ceph/keys/pull/32
https://github.com/ceph/ceph-sepia-secrets/pull/120

Actions #2

Updated by David Galloway almost 8 years ago

  • Status changed from In Progress to 4

Oleh,

You should have access to the Sepia lab now. Please verify you're able to connect to the vpn and ssh using the private key matching the pubkey you provided.

Thanks.

Actions #3

Updated by Oleh Prypin almost 8 years ago

I was able to connect to the VPN (no errors in logs, "Initialization Sequence Completed"), but I'm having some trouble, possibly just with DNS.

ssh and any other program says "Could not resolve hostname teuthology.front.sepia.ceph.com: Name or service not known". Am I missing some step? Do I need to manually add a DNS server?

Thanks.

Actions #4

Updated by David Galloway almost 8 years ago

Our DNS setup is a little wonky. We've been providing private IPs via a public DNS server that has the *.sepia.ceph.com domain delegated to it.

Try adding 172.21.0.10 to your resolv.conf for now. We'll be switching to a different setup where the openvpn server will push a DNS server eventually.

Actions #5

Updated by Nathan Cutler almost 8 years ago

Public DNS servers should be able to resolve that address:

$ host teuthology.front.sepia.ceph.com 8.8.8.8
Using domain server:
Name: 8.8.8.8
Address: 8.8.8.8#53
Aliases: 

teuthology.front.sepia.ceph.com has address 172.21.9.23
teuthology.front.sepia.ceph.com mail is handled by 0 mx1.sub4.homie.mail.dreamhost.com.
teuthology.front.sepia.ceph.com mail is handled by 0 mx2.sub4.homie.mail.dreamhost.com.
Actions #6

Updated by Oleh Prypin almost 8 years ago

David, I've tried with that name server but it didn't help.

Thank you, Nathan, adding 8.8.8.8 immediately solves this, and I was able to log in: oprypin@teuthology:~$

For some reason, my normal nameserver gives this response:

host teuthology.front.sepia.ceph.com 192.168.1.1
Using domain server:
Name: 192.168.1.1
Address: 192.168.1.1#53
Aliases: 

teuthology.front.sepia.ceph.com mail is handled by 0 mx2.sub4.homie.mail.dreamhost.com.
teuthology.front.sepia.ceph.com mail is handled by 0 mx1.sub4.homie.mail.dreamhost.com.

192.168.1.1 is the address of my router which probably just uses whatever the ISP says. Never had problems like this before.

Actions #7

Updated by David Galloway almost 8 years ago

That's interesting. Just out of curiosity, can you log into your router and tell me what DNS servers it's using?

Actions #8

Updated by David Galloway almost 8 years ago

  • Status changed from 4 to Resolved
Actions #9

Updated by Anonymous almost 5 years ago

Hey David,
I am having the same issue, I can authenticate and log can track Initialization Sequence Completed, yet I can't ssh to remote system. I am using this command

`ssh -vv -i /home/d/.ssh/id_rsa
`
which outputs:

`
OpenSSH_7.8p1, OpenSSL 1.1.0i-fips 14 Aug 2018
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Reading configuration data /etc/ssh/ssh_config.d/05-redhat.conf
debug1: Reading configuration data /etc/crypto-policies/back-ends/openssh.config
debug1: /etc/ssh/ssh_config.d/05-redhat.conf line 8: Applying options for *
debug2: resolving "senta04.front.sepia.ceph.com" port 22
debug2: ssh_connect_direct
debug1: Connecting to senta04.front.sepia.ceph.com [172.21.9.34] port 22.
debug1: connect to address 172.21.9.34 port 22: Connection timed out
ssh: connect to host senta04.front.sepia.ceph.com port 22: Connection timed out
`

Also added the `172.21.0.51` to resolv.conf file. Nothing helped.

Actions

Also available in: Atom PDF