Infrastructure » sepia

Hey Gil can I use the username "gbregman" instead of "gbregman@gil-vm"? our gateway is not accepting usernames with the "@" sign

Thanks
Adam

Adam, sure, no problem. I just followed Roy's example.Do you want me to run sepia/new-client again using "gbregman"?

No, only the username needs to change

Hey Gil Bregman,

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

I try to follow the instructions in https://wiki.sepia.ceph.com/doku.php?id=vpnaccess but fails. I'm using a VirtBox VM running on a Windows system. The VM runs as a Red Hat 9.2 machine:

[root@gil-vm ~]# cat /etc/os-release
NAME="Red Hat Enterprise Linux" 
VERSION="9.2 (Plow)" 
ID="rhel" 
ID_LIKE="fedora" 
VERSION_ID="9.2" 
PLATFORM_ID="platform:el9" 
PRETTY_NAME="Red Hat Enterprise Linux 9.2 (Plow)" 
ANSI_COLOR="0;31" 
LOGO="fedora-logo-icon" 
CPE_NAME="cpe:/o:redhat:enterprise_linux:9::baseos" 
HOME_URL="https://www.redhat.com/" 
DOCUMENTATION_URL="https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9" 
BUG_REPORT_URL="https://bugzilla.redhat.com/" 

REDHAT_BUGZILLA_PRODUCT="Red Hat Enterprise Linux 9" 
REDHAT_BUGZILLA_PRODUCT_VERSION=9.2
REDHAT_SUPPORT_PRODUCT="Red Hat Enterprise Linux" 
REDHAT_SUPPORT_PRODUCT_VERSION="9.2" 
[root@gil-vm ~]#

When I try to restart the openvpn service I get an error:

[root@gil-vm ~]# systemctl restart openvpn-client@sepia
Job for openvpn-client@sepia.service failed because the control process exited with error code.
See "systemctl status openvpn-client@sepia.service" and "journalctl -xeu openvpn-client@sepia.service" for details.
[root@gil-vm ~]#

And:

[root@gil-vm openvpn]# systemctl status openvpn-client@sepia.service
× openvpn-client@sepia.service - OpenVPN tunnel for sepia
     Loaded: loaded (/usr/lib/systemd/system/openvpn-client@.service; enabled; preset: disabled)
     Active: failed (Result: exit-code) since Mon 2023-07-31 10:42:51 IDT; 17s ago
       Docs: man:openvpn(8)
             https://community.openvpn.net/openvpn/wiki/Openvpn24ManPage
             https://community.openvpn.net/openvpn/wiki/HOWTO
    Process: 3256 ExecStart=/usr/sbin/openvpn --suppress-timestamps --nobind --config sepia.conf (code=exited, status=1/FAILURE)
   Main PID: 3256 (code=exited, status=1/FAILURE)
        CPU: 12ms

Jul 31 10:42:51 gil-vm systemd[1]: Starting OpenVPN tunnel for sepia...
Jul 31 10:42:51 gil-vm openvpn[3256]: Options error: In [CMD-LINE]:1: Error opening configuration file: sepia.conf
Jul 31 10:42:51 gil-vm openvpn[3256]: Use --help for more information.
Jul 31 10:42:51 gil-vm systemd[1]: openvpn-client@sepia.service: Main process exited, code=exited, status=1/FAILURE
Jul 31 10:42:51 gil-vm systemd[1]: openvpn-client@sepia.service: Failed with result 'exit-code'.
Jul 31 10:42:51 gil-vm systemd[1]: Failed to start OpenVPN tunnel for sepia.
[root@gil-vm openvpn]#

It seems that the configuration file is not found. I can see it in:

[root@gil-vm openvpn]# ll /etc/openvpn/sepia.conf
lrwxrwxrwx. 1 root root 17 Jul 27 17:57 /etc/openvpn/sepia.conf -> sepia/client.conf
[root@gil-vm openvpn]# ll /etc/openvpn/sepia/client.conf
-rw-r--r-- 1 1105 1105 274 Jul 31 09:17 /etc/openvpn/sepia/client.conf
[root@gil-vm openvpn]#

anything I am doing wrong?

Fixed over Slack
I used this hash "gbregman YfVXOuxi4a6ya8FOLzugGQ b852da781c70bcee54065b86bee3d0b0ac6796bb1d2660616d3ae83a071ac6d6"

Adam, I think you can close this ticket by now.