Infrastructure » sepia

adam kraitman wrote:

Hey Shilpa MJ Are these new/additional or replacement credentials?

Hi Adam,

These are replacement credentials.

Hey Shilpa MJ,

You should have access to the Sepia lab now. Please verify you're able to connect to the vpn and ssh smanjara@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

If you plan on scheduling tests, one of the options you'll need to set with teuthology-suite is -p, --priority. Please refrain from using a priority lower than 101 (lower number = higher priority). When a high priority is used, it locks up too many testnodes at once and prevents other developers from testing changes.

Thanks.

adam kraitman wrote:

Hey Shilpa MJ,

You should have access to the Sepia lab now. Please verify you're able to connect to the vpn and ssh smanjara@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

Thanks Adam. I followed https://wiki.sepia.ceph.com/doku.php?id=vpnaccess#vpn_client_access on my fedora37. I am not able to start the service. Probably due to permission error:

$ systemctl restart openvpn-client@sepia
Job for openvpn-client@sepia.service failed because the control process exited with error code.

$ systemctl status openvpn-client@sepia
× openvpn-client@sepia.service - OpenVPN tunnel for sepia
Loaded: loaded (/usr/lib/systemd/system/openvpn-client@.service; disabled; preset: disabled)
Active: failed (Result: exit-code) since Wed 2023-04-19 12:54:45 EDT; 6s ago

Apr 19 12:54:45 li-b46676cc-2f05-11b2-a85c-9b92c8acacdf.ibm.com systemd¹: Starting openvpn-client@sepia.service - OpenVPN tunnel for sepia...
Apr 19 12:54:45 li-b46676cc-2f05-11b2-a85c-9b92c8acacdf.ibm.com openvpn²²⁰³⁰²: Options error: In [CMD-LINE]:1: Error opening configuration file: sepia.conf

smanjara:~$ ls l /etc/openvpn/sepia.conf
-rw-r--r-. 1 1106 1106 274 Apr 19 10:53 /etc/openvpn/sepia.conf
smanjara:~$ ls l /etc/openvpn/sepia/
total 20
-rw-r--r-. 1 1106 1106 1241 Mar 22 2015 ca.crt
rw-r--r-. 1 1106 1106 290 Apr 19 12:51 client.conf
rwxr-xr-x. 1 1106 1106 1950 Oct 27 2020 new-client
-rw------. 1 root root 144 Mar 31 16:48 secret
r--r----. 1 1106 1106 636 Mar 22 2015 tlsauth

please fix the sepia.conf link as the following:
lrwxrwxrwx 1 root root 17 Jan 8 18:34 sepia.conf -> sepia/client.conf

Hi Adam,

I fixed the link:
lrwxrwxrwx. 1 root root 17 May 10 12:33 sepia.conf -> sepia/client.conf

rw-r--r-. 1 1106 1106 274 May 10 12:33 sepia/client.conf

openvpn still fails with Error opening configuration file: sepia.conf

Please disable SELinux if it's enabled

adam kraitman wrote:

Please disable SELinux if it's enabled

Hi Adam,

Thanks. I disabled selinux and restarted. Still have the same issue.