Infrastructure » sepia

Hi Adam,

Yes, Kalpesh is an intern working for my team in BLR.

thanks,

Matt

Hi Kalpesh Pandya,

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

adam kraitman wrote:

Hi Kalpesh Pandya,

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

Hello Adam,

I was not able to access when trying to use: ssh kapandya@teuthology.front.sepia.ceph.com
Then I went through https://tracker.ceph.com/issues/43518 and used the command: rm -rf /etc/openvpn/*sepia* /etc/openvpn-client/*sepia*

So following is my new Hashed VPN Credentials:
kapandya@thinkpad Uw1JHj0kPIqSd9iOJ68TNg 46badc3b5cd150bfb74daf4300c8329491000521738ba70455631aa4a47e42c0

Can you please give me the access again.

Sorry for the inconvenience caused.

Thank you in advance,
Kalpesh Pandya

Hey, Kalpesh Pandya
Please try now, vpn hash updated

Thanks,

Adam

adam kraitman wrote:

Hey, Kalpesh Pandya
Please try now, vpn hash updated

Thanks,

Adam

Hello Adam,

I'm still facing some issue as mentioned below:

1) I followed the steps mentioned in https://wiki.sepia.ceph.com/doku.php?id=vpnaccess. But when I'm trying to execute the last command: sudo systemctl enable openvpn-client@sepia it shows me the following output: ssh: connect to host teuthology.front.sepia.ceph.com port 22: Connection timed out.

FYI:

1) I'm connected to the VPN

2) I'm new to this so, it would be great if you help me out for solving this issue.

Thank you in advance.

Kalpesh Pandya

Thank you Kalpesh Pandya,

Can you please paste the output of "journalctl -u openvpn-client@sepia"

Hey Kalpesh Pandya, I think it happens because SELinux is active please try editing /etc/sysconfig/selinux and setting SELINUX=permissive, this will require a reboot and after the reboot run the following commands
sudo systemctl enable openvpn-client@sepia
sudo systemctl start openvpn-client@sepia
and check the status
sudo systemctl status openvpn-client@sepia

Thanks,

Adam

adam kraitman wrote:

Hey Kalpesh Pandya, I think it happens because SELinux is active please try editing /etc/sysconfig/selinux and setting SELINUX=permissive, this will require a reboot and after the reboot run the following commands
sudo systemctl enable openvpn-client@sepia
sudo systemctl start openvpn-client@sepia
and check the status
sudo systemctl status openvpn-client@sepia

Thanks,

Adam

Hey Adam,

I got your point of editing selinux, but I didn't got your reboot part. Can you please guide me that how can I do this?

Thank you in advance.

Kalpesh Pandya

Hi Kalpesh Pandya,
It means that after changing the SElinux settings you will need to reboot your laptop

adam kraitman wrote:

Hi Kalpesh Pandya,
It means that after changing the SElinux settings you will need to reboot your laptop

Hello Adam,

Will follow the steps and get back to you.

Thank you,

Kalpesh Pandya

Hi, Any update ?

adam kraitman wrote:

Hi, Any update ?

Hey, was little busy with some other work. Now I'm trying to do this and will get back to you soon.

Sorry for the inconvenience caused.

Thanks,
Kalpesh Pandya

adam kraitman wrote:

Hi Kalpesh Pandya,
It means that after changing the SElinux settings you will need to reboot your laptop

I opened the file selinux but it's a read only file. So it is not allowing me to edit SELINUX to permissive. Can you please help me out here?

Kalpesh Pandya wrote:

adam kraitman wrote:

Hi Kalpesh Pandya,
It means that after changing the SElinux settings you will need to reboot your laptop

I opened the file selinux but it's a read only file. So it is not allowing me to edit SELINUX to permissive. Can you please help me out here?

Hello,

Nevermind this.

I changed the settings of selinux to permissive and ran the said commands after the reboot. Following is the output for 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: disabled)
Active: failed (Result: exit-code) since Mon 2020-04-20 12:23:14 IST; 5s ago
Docs: man:openvpn(8)
https://community.openvpn.net/openvpn/wiki/Openvpn24ManPage
https://community.openvpn.net/openvpn/wiki/HOWTO
Process: 4009 ExecStart=/usr/sbin/openvpn --suppress-timestamps --nobind --config sepia.conf (code=exited, status=1/FAILURE)
Main PID: 4009 (code=exited, status=1/FAILURE)
Status: "Pre-connection initialization successful"

Apr 20 12:23:10 localhost.localdomain openvpn⁴⁰⁰⁹: WARNING: file 'sepia/tlsauth' is group or others accessible
Apr 20 12:23:10 localhost.localdomain openvpn⁴⁰⁰⁹: OpenVPN 2.4.8 x86_64-redhat-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Nov 1 2019
Apr 20 12:23:10 localhost.localdomain openvpn⁴⁰⁰⁹: library versions: OpenSSL 1.1.1d FIPS 10 Sep 2019, LZO 2.08
Apr 20 12:23:10 localhost.localdomain systemd¹: Started OpenVPN tunnel for sepia.
Apr 20 12:23:10 localhost.localdomain openvpn⁴⁰⁰⁹: Outgoing Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication
Apr 20 12:23:10 localhost.localdomain openvpn⁴⁰⁰⁹: Incoming Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication
Apr 20 12:23:14 localhost.localdomain openvpn⁴⁰⁰⁹: failed to find GID for group nogroup
Apr 20 12:23:14 localhost.localdomain openvpn⁴⁰⁰⁹: Exiting due to fatal error
Apr 20 12:23:14 localhost.localdomain systemd¹: openvpn-client@sepia.service: Main process exited, code=exited, status=1/FAILURE
Apr 20 12:23:14 localhost.localdomain systemd¹: openvpn-client@sepia.service: Failed with result 'exit-code'.

Thanks,
Kalpesh Pandya

Kalpesh Pandya wrote:

Kalpesh Pandya wrote:

adam kraitman wrote:

Hi Kalpesh Pandya,
It means that after changing the SElinux settings you will need to reboot your laptop

I opened the file selinux but it's a read only file. So it is not allowing me to edit SELINUX to permissive. Can you please help me out here?

Hello,

Nevermind this.

I changed the settings of selinux to permissive and ran the said commands after the reboot. Following is the output for 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: disabled)
Active: failed (Result: exit-code) since Mon 2020-04-20 12:23:14 IST; 5s ago
Docs: man:openvpn(8)
https://community.openvpn.net/openvpn/wiki/Openvpn24ManPage
https://community.openvpn.net/openvpn/wiki/HOWTO
Process: 4009 ExecStart=/usr/sbin/openvpn --suppress-timestamps --nobind --config sepia.conf (code=exited, status=1/FAILURE)
Main PID: 4009 (code=exited, status=1/FAILURE)
Status: "Pre-connection initialization successful"

Apr 20 12:23:10 localhost.localdomain openvpn⁴⁰⁰⁹: WARNING: file 'sepia/tlsauth' is group or others accessible
Apr 20 12:23:10 localhost.localdomain openvpn⁴⁰⁰⁹: OpenVPN 2.4.8 x86_64-redhat-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Nov 1 2019
Apr 20 12:23:10 localhost.localdomain openvpn⁴⁰⁰⁹: library versions: OpenSSL 1.1.1d FIPS 10 Sep 2019, LZO 2.08
Apr 20 12:23:10 localhost.localdomain systemd¹: Started OpenVPN tunnel for sepia.
Apr 20 12:23:10 localhost.localdomain openvpn⁴⁰⁰⁹: Outgoing Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication
Apr 20 12:23:10 localhost.localdomain openvpn⁴⁰⁰⁹: Incoming Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication
Apr 20 12:23:14 localhost.localdomain openvpn⁴⁰⁰⁹: failed to find GID for group nogroup
Apr 20 12:23:14 localhost.localdomain openvpn⁴⁰⁰⁹: Exiting due to fatal error
Apr 20 12:23:14 localhost.localdomain systemd¹: openvpn-client@sepia.service: Main process exited, code=exited, status=1/FAILURE
Apr 20 12:23:14 localhost.localdomain systemd¹: openvpn-client@sepia.service: Failed with result 'exit-code'.

Thanks,
Kalpesh Pandya

Hello adam,

Can you please help me out over here?

Thanks,
Kalpesh Pandya

Hey, Can you please paste the output of
sudo ls -l /etc/openvpn/client/sepia
i want to see the user and group permission

adam kraitman wrote:

Hey, Can you please paste the output of
sudo ls -l /etc/openvpn/client/sepia
i want to see the user and group permission

Here's the output of this:

total 20
rw-r--r-. 1 kapandya kapandya 1241 Mar 23 2015 ca.crt
rw-r--r-. 1 kapandya kapandya 273 Mar 23 2015 client.conf
rwxr-xr-x. 1 kapandya kapandya 1737 Mar 23 2015 new-client
-rw------. 1 root root 105 Mar 6 11:04 secret
r--r----. 1 kapandya kapandya 636 Mar 23 2015 tlsauth

Hi Kalpesh Pandya,
I suspect that maybe you ran the new-client script twice by accident
I would ask you to please run:
sudo rm -rf /etc/openvpn/*sepia* /etc/openvpn-client/*sepia*

And do the process again https://wiki.sepia.ceph.com/doku.php?id=vpnaccess
then paste here your new hashed VPN credentials

Thanks

adam kraitman wrote:

Hi Kalpesh Pandya,
I suspect that maybe you ran the new-client script twice by accident
I would ask you to please run:
sudo rm -rf /etc/openvpn/*sepia* /etc/openvpn-client/*sepia*

And do the process again https://wiki.sepia.ceph.com/doku.php?id=vpnaccess
then paste here your new hashed VPN credentials

Thanks

Hello,

I followed the steps on the given website, but while executing "sudo ./sepia/new-client kapandya@thinkpad" command I see the following error:

Traceback (most recent call last):
File "./sepia/new-client", line 57, in <module>
os.symlink(os.path.join(base, 'client.conf'), '../sepia.conf')
OSError: [Errno 17] File exists

Thanks,
Kalpesh Pandya

Sorry i had a typo, Please run sudo rm -rf /etc/openvpn/client/*sepia*
And do the process again https://wiki.sepia.ceph.com/doku.php?id=vpnaccess
then paste here your new hashed VPN credentials

adam kraitman wrote:

Sorry i had a typo, Please run sudo rm -rf /etc/openvpn/client/*sepia*
And do the process again https://wiki.sepia.ceph.com/doku.php?id=vpnaccess
then paste here your new hashed VPN credentials

Here are the credentials:

kapandya@thinkpad g4JoonWShBhyS6fEdaHh7A 2990a987bf7afee6e3c8b5236b3dac813a57dbdce47ec63965c40b1b7bdafd67

Thanks,
Kalpesh Pandya

Hi Kalpesh Pandya,

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

adam kraitman wrote:

Hi Kalpesh Pandya,

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

Hello,

I tried to run ssh kapandya@teuthology.front.sepia.ceph.com but I'm still getting the following:

ssh: connect to host teuthology.front.sepia.ceph.com port 22: Connection timed out

P.S: I'm already connected to VPN.

Thanks,
Kalpesh Pandya

Check that you can ping and telnet teuthology.front.sepia.ceph.com port 22
ping teuthology.front.sepia.ceph.com
telnet teuthology.front.sepia.ceph.com 22

adam kraitman wrote:

Check that you can ping and telnet teuthology.front.sepia.ceph.com port 22
ping teuthology.front.sepia.ceph.com
telnet teuthology.front.sepia.ceph.com 22

Hello,

ping teuthology.front.sepia.ceph.com gives me this(I terminated after sometime because it was not showing anything apart from 1st line below):

PING teuthology.front.sepia.ceph.com (172.21.0.51) 56(84) bytes of data.
^C
--- teuthology.front.sepia.ceph.com ping statistics ---
285 packets transmitted, 0 received, 100% packet loss, time 1132ms

And, telnet teuthology.front.sepia.ceph.com 22 gives:

Trying 172.21.0.51...
telnet: connect to address 172.21.0.51: Connection timed out

Thanks,
Kalpesh Pandya

It seems that you are blocked by a firewall, it could be your local iptables that is blocking you or a firewall that is located somewhere in your network that is blocking you from reaching teuthology.front.sepia.ceph.com, Please check

Cheers

Adam

adam kraitman wrote:

It seems that you are blocked by a firewall, it could be your local iptables that is blocking you or a firewall that is located somewhere in your network that is blocking you from reaching teuthology.front.sepia.ceph.com, Please check

Cheers

Adam

How can I check that?

You can check this with the IT team they could help you with that

adam kraitman wrote:

You can check this with the IT team they could help you with that

Okay, after doing this I'll get back to you.

Thanks,
Kalpesh Pandya

The error message is clearly in the OpenVPN output.

Apr 20 12:23:14 localhost.localdomain openvpn4009: failed to find GID for group nogroup

Just to clarify, the Red Hat VPN is different than the Sepia lab VPN. The Sepia VPN has nothing to do with Red Hat's network.

The fix for failed to find GID for group nogroup is in the documentation under Linux Gotchas

https://wiki.sepia.ceph.com/doku.php?id=vpnaccess#linux

David Galloway wrote:

The error message is clearly in the OpenVPN output.

[...]

Just to clarify, the Red Hat VPN is different than the Sepia lab VPN. The Sepia VPN has nothing to do with Red Hat's network.

The fix for failed to find GID for group nogroup is in the documentation under Linux Gotchas

https://wiki.sepia.ceph.com/doku.php?id=vpnaccess#linux

Should I try to login again?

Kalpesh Pandya wrote:

David Galloway wrote:

The error message is clearly in the OpenVPN output.

[...]

Just to clarify, the Red Hat VPN is different than the Sepia lab VPN. The Sepia VPN has nothing to do with Red Hat's network.

The fix for failed to find GID for group nogroup is in the documentation under Linux Gotchas

https://wiki.sepia.ceph.com/doku.php?id=vpnaccess#linux

Should I try to login again?

As per https://wiki.sepia.ceph.com/doku.php?id=vpnaccess#linux in the command "sed -i 's/nobody/openvpn/g' /etc/openvpn/sepia/client.conf" the path is incorrect I guess. It should be /etc/openvpn/client/sepia/client.conf

Please check for the same.

Thanks,
Kalpesh Pandya

Kalpesh Pandya wrote:

Kalpesh Pandya wrote:

David Galloway wrote:

The error message is clearly in the OpenVPN output.

[...]

Just to clarify, the Red Hat VPN is different than the Sepia lab VPN. The Sepia VPN has nothing to do with Red Hat's network.

The fix for failed to find GID for group nogroup is in the documentation under Linux Gotchas

https://wiki.sepia.ceph.com/doku.php?id=vpnaccess#linux

Should I try to login again?

As per https://wiki.sepia.ceph.com/doku.php?id=vpnaccess#linux in the command "sed -i 's/nobody/openvpn/g' /etc/openvpn/sepia/client.conf" the path is incorrect I guess. It should be /etc/openvpn/client/sepia/client.conf

Please check for the same.

Thanks,
Kalpesh Pandya

Also, after going through https://wiki.sepia.ceph.com/doku.php?id=vpnaccess. I'm able to access ssh kapandya@teuthology.front.sepia.ceph.com.

But I've forgotten the password for that. Can you help me out for this?

Sorry for the inconvenience caused.

Thanks,
Kalpesh Pandya

I am seeing in the gateway logs that you managed to connect today

Please run the following:

sudo service openvpn restart
OR
sudo systemctl restart openvpn@sepia
OR
sudo systemctl restart openvpn-client@sepia

1. Try all 3. One of them should work.
2. Whichever works, and enable the systemd service

sudo systemctl enable openvpn@sepia
OR
sudo systemctl enable openvpn-client@sepia

And sudo systemctl status openvpn@sepia
OR
sudo systemctl status openvpn-client@sepia

And paste the output

adam kraitman wrote:

I am seeing in the gateway logs that you managed to connect today

Please run the following:

sudo service openvpn restart
OR
sudo systemctl restart openvpn@sepia
OR
sudo systemctl restart openvpn-client@sepia

1. Try all 3. One of them should work.
2. Whichever works, and enable the systemd service

sudo systemctl enable openvpn@sepia
OR
sudo systemctl enable openvpn-client@sepia

And sudo systemctl status openvpn@sepia
OR
sudo systemctl status openvpn-client@sepia

And paste the output

Here's the output of 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: disabled)
Active: active (running) since Sun 2020-05-10 19:03:17 IST; 55s ago
Docs: man:openvpn(8)
https://community.openvpn.net/openvpn/wiki/Openvpn24ManPage
https://community.openvpn.net/openvpn/wiki/HOWTO
Main PID: 409660 (openvpn)
Status: "Initialization Sequence Completed"
Tasks: 1 (limit: 4915)
Memory: 1.9M
CGroup: /system.slice/system-openvpn\x2dclient.slice/openvpn-client@sepia.service
└─409660 /usr/sbin/openvpn --suppress-timestamps --nobind --config sepia.conf

May 10 19:03:20 localhost.localdomain openvpn⁴⁰⁹⁶⁶⁰: [openvpn-sepia] Peer Connection Initiated with [AF_INET]8.43.84.129:1194
May 10 19:03:22 localhost.localdomain openvpn⁴⁰⁹⁶⁶⁰: Data Channel: using negotiated cipher 'AES-256-GCM'
May 10 19:03:22 localhost.localdomain openvpn⁴⁰⁹⁶⁶⁰: Outgoing Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
May 10 19:03:22 localhost.localdomain openvpn⁴⁰⁹⁶⁶⁰: Incoming Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
May 10 19:03:22 localhost.localdomain openvpn⁴⁰⁹⁶⁶⁰: TUN/TAP device sepia0 opened
May 10 19:03:22 localhost.localdomain openvpn⁴⁰⁹⁶⁶⁰: /sbin/ip link set dev sepia0 up mtu 1500
May 10 19:03:22 localhost.localdomain openvpn⁴⁰⁹⁶⁶⁰: /sbin/ip addr add dev sepia0 local 172.21.49.130 peer 172.21.49.129
May 10 19:03:22 localhost.localdomain openvpn⁴⁰⁹⁶⁶⁰: GID set to openvpn
May 10 19:03:22 localhost.localdomain openvpn⁴⁰⁹⁶⁶⁰: UID set to openvpn
May 10 19:03:22 localhost.localdomain openvpn⁴⁰⁹⁶⁶⁰: Initialization Sequence Completed

According to the output you are connected, you can start working in the lab

adam kraitman wrote:

According to the output you are connected, you can start working in the lab

Yes, that's true but to login using ssh kapandya@teuthology.front.sepia.ceph.com it requires a password and I've forgotten the password for that. So how can I reset this?

Thanks,
Kalpesh Pandya

Try now, The access is with the ssh key no password is needed

adam kraitman wrote:

Try now, The access is with the ssh key no password is needed

I tried to use ssh kapandya@teuthology.front.sepia.ceph.com but it asks for the following and I've forgotten the same.

kapandya@teuthology.front.sepia.ceph.com's password:

Thanks,
Kalpesh Pandya

Do you still have the SSH private key matching the public key here? https://github.com/ceph/keys/blob/master/ssh/kapandya.pub

Try ssh -i ~/.ssh/id_rsa kapandya@teuthology.front.sepia.ceph.com

We don't use passwords in the lab; Just SSH keys.

David Galloway wrote:

Do you still have the SSH private key matching the public key here? https://github.com/ceph/keys/blob/master/ssh/kapandya.pub

Try ssh -i ~/.ssh/id_rsa kapandya@teuthology.front.sepia.ceph.com

We don't use passwords in the lab; Just SSH keys.

Hello,

The ssh private key doesn't match the public key at https://github.com/ceph/keys/blob/master/ssh/kapandya.pub.

So, how can we solve this?

Thanks,
Kalpesh Pandya

Kalpesh Pandya wrote:

So, how can we solve this?

Give us the correct public key...

Kalpesh Pandya wrote:

David Galloway wrote:

Kalpesh Pandya wrote:

So, how can we solve this?

Give us the correct public key...

I checked id_rsa.pub and the pub key there is the same as in https://github.com/ceph/keys/blob/master/ssh/kapandya.pub

Sorry for the wrong reply. It happened because I checked id_rsa.

I'm attaching the ssh private key (provided in id_rsa file) along with this reply.

PFA.

Sorry for the inconvenience caused.

Thanks,
Kalpesh Pandya

Hello,

Any updates on this? Waiting for the response.

Thanks,
Kalpesh Pandya

Hey Kalpesh Pandya,
Using the privet key run
ssh -i ~/.ssh/id_rsa kapandya@teuthology.front.sepia.ceph.com

adam kraitman wrote:

Hey Kalpesh Pandya,
Using the privet key run
ssh -i ~/.ssh/id_rsa kapandya@teuthology.front.sepia.ceph.com

Hey adam,

Finally it's running with the following output:

Welcome to Ubuntu 18.04.4 LTS (GNU/Linux 4.15.0-96-generic x86_64)

• Documentation: https://help.ubuntu.com
• Management: https://landscape.canonical.com
• Support: https://ubuntu.com/advantage

• Ubuntu 20.04 LTS is out, raising the bar on performance, security,
  and optimisation for Intel, AMD, Nvidia, ARM64 and Z15 as well as
  AWS, Azure and Google Cloud.

  https://ubuntu.com/blog/ubuntu-20-04-lts-arrives

• Canonical Livepatch is available for installation.
  - Reduce system reboots and improve kernel security. Activate at:
  https://ubuntu.com/livepatch

The programs included with the Ubuntu system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Ubuntu comes with ABSOLUTELY NO WARRANTY, to the extent permitted by
applicable law.

kapandya@teuthology:~$

I hope nothing is wrong in the output.

Thanks,
Kalpesh Pandya

Good, I am glad it works

You should never share your private key for any reason.

Please erase both the private and public keys on your machine (rm -f ~/.ssh/id_rsa*), generate a new pair (ssh-keygen -t rsa) and share ONLY the public key with us.

Hey try now i added you new key

adam kraitman wrote:

Hey try now i added you new key

Yeah it's working fine now.

Thanks,
Kalpesh Pandya