search

ReproNim / reproman

ReproMan (AKA NICEMAN, AKA ReproNim TRD3)
https://reproman.readthedocs.io
Other
24 stars 14 forks source link

cannot login to ec2 instance (NITRC CE 5.0) in west-2 zone #487

Open yarikoptic opened 5 years ago

yarikoptic commented 5 years ago 
(git)lena:~/proj/repronim/reproman-master[master]
$> reproman create -t aws-ec2 my-nitrc-west-2-2 -b region_name=us-west-2 image=ami-02faf30d364b36946 instance_type=t2.medium
You did not specify an EC2 SSH key-pair name to use when creating your EC2
environment.
Please enter a unique name to create a new key-pair or press [enter] to exit: my-nitrc-west-2-2

2019-11-14 15:37:53,804 [INFO   ] Created private key file /home/yoh/.local/share/reproman/ec2_keys/my-nitrc-west-2-2.pem 
2019-11-14 15:37:55,313 [INFO   ] Waiting for EC2 instance i-053178c896afa9706 to start running... 
2019-11-14 15:38:25,845 [INFO   ] EC2 instance i-053178c896afa9706 is running! 
2019-11-14 15:38:25,845 [INFO   ] Waiting for EC2 instance i-053178c896afa9706 to complete initialization... 
2019-11-14 15:41:59,063 [INFO   ] EC2 instance i-053178c896afa9706 initialized! 
2019-11-14 15:41:59,088 [INFO   ] Created the environment my-nitrc-west-2-2 
(dev3) 1 3704.....................................:Thu 14 Nov 2019 03:41:59 PM EST:.
(git)lena:~/proj/repronim/reproman-master[master]
$> reproman login my-nitrc-west-2-2
2019-11-14 15:42:37,868 [ERROR  ] [Errno 110] Connection timed out [client.py:<lambda>:349] (TimeoutError) 
(dev3) 1 3709 ->1.....................................:Thu 14 Nov 2019 03:42:37 PM EST:.
(git)lena:~/proj/repronim/reproman-master[master]
$> reproman delete my-nitrc-west-2-2
Delete the resource 'my-nitrc-west-2-2'? (ID: i-053178c896afa9706) (choices: yes, [no], y, n): y

2019-11-14 15:43:20,628 [INFO   ] Deleted the environment my-nitrc-west-2-2

This is already second instance/attempt. Any idea on what is going on? could anyone replicate?

yarikoptic commented 5 years ago

the same happens if I use another AMI (debian buster listed on https://wiki.debian.org/Cloud/AmazonEC2Image/Buster), with the same success

But when I started an instance (from a different amazon account though) manually in the dashboard - I could ssh in. So it is either some limitation of our repronim account, or how reproman starts an instance

yarikoptic commented 5 years ago

@mjtravers I will leave this puzzle for you. I ended up just manually (aws web ui) creating an instance in that region and ssh'ing into it