Support #51196
closedSepia Lab Access Request
0%
Description
1) Do you just need VPN access or will you also be running teuthology jobs?
I will be running teuthology jobs. I am an existing user and when I updated my system to Fedora34, I am facing issues with connecting to teuthology machines. Hence I am trying to reconfigure the same.
2) Desired Username:
soumyakoduri
3) Alternate e-mail address(es) we can reach you at:
skoduri@redhat.com
4) If you don't already have an established history of code contributions to Ceph, is there an existing community or core developer you've worked with who has reviewed your work and can vouch for your access request?
part Ceph RGW development team
If you answered "No" to # 4, please answer the following (paste directly below the question to keep indentation):
4a) Paste a link to a Blueprint or planning doc of yours that was reviewed at a Ceph Developer Monthly.
4b) Paste a link to an accepted pull request for a major patch or feature.
4c) If applicable, include a link to the current project (planning doc, dev branch, or pull request) that you are looking to test.
5) Paste your SSH public key(s) between the pre
tags
ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABgQCrGYBGPDQqn+2jnxKhDurSrAJvTT8dZMYGVCt6NbjpFhDFYtyvrF8Jv5NKBQynG18LwscN7a57L0Oq0e4jOEPRz//CDcAfP+L6p45L4BdUzTysN4+rQ7waMnIiYp7VjSswhGH/BnYIVKwmDqzM2fo1w/oLIT6mgwUYqAdceeswAkXBt7jgagL8ox3E4oHBqER7f60AHdTviuW953t5luVQiMjyF2fOwZuo2ycufIzBee0CwS+xyRuJQwdgD3HL4Qs2vtBCX+H8n3wC6A9JrMA5tzCDr5VZKBJZURIniwvaXfJodjO4SvBL5jAfXoMqriv8ZWHbap2fk82YE8/uPqNvSISjixJEBgQinklZ+iAOYm5tfPbhPM/8ErpN/yJ0EoGRn+nj6X6nAjXAIk3AENopeqtM7mLZ26RFIuEV5ld7eqUvAfiy6Hk2LH9Q1Z4CXaxD0gDGzUxgdAaaAgLAR4btWi2n7Tb7ZNDdOfctg2ya9ftzZBOHvCaVXSpJCry/GMU= skoduri@localhost.localdomain
6) Paste your hashed VPN credentials between the pre
tags (Format: user@hostname 22CharacterSalt 65CharacterHashedPassword
)
skoduri@localhost w/vFHwM/x4hUGlKJCteKiA 97933f044fdd8b3cf57ad744ce032728b06f354b0d719790def82b2f5b9a6133
Updated by adam kraitman almost 3 years ago
- Category set to User access
- Status changed from New to In Progress
- Assignee set to adam kraitman
Updated by adam kraitman almost 3 years ago
Hey Soumya Koduri, Are these new/additional or replacement credentials?
Updated by Soumya Koduri almost 3 years ago
adam kraitman wrote:
Hey Soumya Koduri, Are these new/additional or replacement credentials?
They are replacement credentials. Thanks!
Updated by adam kraitman almost 3 years ago
Hi Soumya Koduri,
You should have access to the Sepia lab now. Please verify you're able to connect to the vpn and ssh soumyakoduri@teuthology.front.sepia.ceph.com using the private key matching the pubkey you provided.
Be sure to check out the following links for final workstation setup steps:
https://wiki.sepia.ceph.com/doku.php?id=vpnaccess#vpn_client_access
https://wiki.sepia.ceph.com/doku.php?id=testnodeaccess#ssh_config
Most developers choose to schedule runs from the shared teuthology VM. For information on that, see http://docs.ceph.com/teuthology/docs/intro_testers.html
Thanks
Updated by Soumya Koduri almost 3 years ago
Hi Adam,
I am still unable to access the teuthology machines. It throws "teuthology.front.sepia.ceph.com: Name or service not known" error.
The openvpn-client is successfully running but its still not able to resolve the hostname. This issue has come up only after I upgraded my system to Fedora34. Re-creating the credentials hasn't helped resolve the issue. Pasting below my config details. Please let me know what may be the issue here. Thanks!
[skoduri@localhost sepia]$ sudo systemctl status openvpn-client@sepia
● openvpn-client@sepia.service - OpenVPN tunnel for sepia
Loaded: loaded (/usr/lib/systemd/system/openvpn-client@.service; enabled; vendor preset:>
Active: active (running) since Mon 2021-06-21 14:47:57 IST; 2s ago
Docs: man:openvpn(8)
...
...
[skoduri@localhost sepia]$ cat client.conf
script-security 1
client
remote vpn.sepia.ceph.com 1194
dev sepia0
dev-type tun
remote-random
resolv-retry infinite
nobind
user openvpn
group openvpn
persist-tun
persist-key
comp-lzo
verb 2
mute 10
remote-cert-tls server
tls-auth sepia/tlsauth 1
ca sepia/ca.crt
auth-user-pass sepia/secret
[skoduri@localhost sepia]$
[skoduri@localhost sepia]$ ssh soumyakoduri@teuthology.front.sepia.ceph.com
ssh: Could not resolve hostname teuthology.front.sepia.ceph.com: Name or service not known
[skoduri@localhost sepia]$
[skoduri@localhost sepia]$ ping vpn.sepia.ceph.com
PING gw.sepia.ceph.com (8.43.84.129) 56(84) bytes of data.
64 bytes from gw.sepia.ceph.com (8.43.84.129): icmp_seq=1 ttl=50 time=330 ms
^C
--- gw.sepia.ceph.com ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 330.375/330.375/330.375/0.000 ms
[skoduri@localhost sepia]$
[skoduri@localhost sepia]$ ping sepia.com
PING sepia.com (5.199.130.140) 56(84) bytes of data.
64 bytes from www.sepia.de (5.199.130.140): icmp_seq=1 ttl=56 time=183 ms
^C
--- sepia.com ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 183.312/183.312/183.312/0.000 ms
[skoduri@localhost sepia]$
[skoduri@localhost sepia]$ ping sepia.ceph.com
ping: sepia.ceph.com: Name or service not known
[skoduri@localhost sepia]$
[skoduri@localhost sepia]$ ping teuthology.front.sepia.ceph.com
ping: teuthology.front.sepia.ceph.com: Name or service not known
[skoduri@localhost sepia]$
Updated by adam kraitman almost 3 years ago
Hey Soumya, If you re-run the new-client script, It's unfortunately not idempotent so if you re-ran it and still have the output, we'll need the new string it printed. If you don't have the output, please re-run it again and send the new string.
Updated by Soumya Koduri almost 3 years ago
Hi Adam,
Sorry for the confusion. The creds I had provided in this tracker are the current latest ones. However I am still unable to login to machines as it throws error "teuthology.front.sepia.ceph.com: Name or service not known" . Any idea how to resolve the same? Thanks!
Updated by adam kraitman almost 3 years ago
Working After updating /etc/dnsmasq.conf
Updated by adam kraitman almost 3 years ago
- Status changed from In Progress to Resolved