761425 – Not able to ssh to running ec2 instances.

Bug 761425 - Not able to ssh to running ec2 instances.

Summary: Not able to ssh to running ec2 instances.

Keywords:
Status:	CLOSED CURRENTRELEASE
Alias:	None
Product:	CloudForms Cloud Engine
Classification:	Retired
Component:	imagefactory
Sub Component:
Version:	1.0.0
Hardware:	Unspecified
OS:	Unspecified
Priority:	unspecified
Severity:	high
Target Milestone:	rc
Assignee:	jrd
QA Contact:	Martin Kočí
Docs Contact:
URL:	https://hp-bl480c-01.rhts.eng.bos.red...
Whiteboard:
Depends On:
Blocks:
TreeView+	depends on / blocked

Reported:	2011-12-08 10:16 UTC by Aziza Karol
Modified:	2013-02-27 04:26 UTC (History)
CC List:	7 users (show)
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:

Attachments	(Terms of Use)
running isntance (229.40 KB, image/png) 2011-12-08 10:17 UTC, Aziza Karol	no flags	Details
system log (63.32 KB, application/octet-stream) 2011-12-08 10:24 UTC, Aziza Karol	no flags	Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Aziza Karol 2011-12-08 10:16:06 UTC

Description of problem:


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
I launched a ec2 deployment in us-east and it is successfully running in aeolus application as  well in aws console.
however when i tried connecting it,i am not able to ssh nor i am able to ping.
  
see attached screenshot.



Not able to ssh:
[root@akarol Desktop]# ssh -i ec2_11_frontend_1323326789_key_70306932362540.pem  root.amazonaws.com
ssh: connect to host ec2-50-16-69-121.compute-1.amazonaws.com port 22: Connection timed out


Not able to ping:
[root@akarol Desktop]# ping ec2-50-16-69-121.compute-1.amazonaws.com
PING ec2-50-16-69-121.compute-1.amazonaws.com (50.16.69.121) 56(84) bytes of data.



AMI ID:
ami-4370bb2a

see attach system logs


Expected results:
should be able to connect.


Additional info:
[root@hp-bl480c-01 ~]# rpm -qa | egrep 'aeolus|imagefactory'
rubygem-imagefactory-console-0.4.0-1.el6.noarch
imagefactory-jeosconf-ec2-rhel-1.0.0rc1-1.el6.noarch
aeolus-conductor-0.7.0-4.el6.noarch
imagefactory-jeosconf-ec2-fedora-1.0.0rc1-1.el6.noarch
aeolus-configure-2.4.0-3.el6.noarch
aeolus-conductor-doc-0.7.0-4.el6.noarch
aeolus-all-0.7.0-4.el6.noarch
rubygem-aeolus-cli-0.2.0-3.el6.noarch
imagefactory-1.0.0rc1-1.el6.noarch
rubygem-aeolus-image-0.2.0-1.el6.noarch
aeolus-conductor-daemons-0.7.0-4.el6.noarch

Comment 1 Aziza Karol 2011-12-08 10:17:00 UTC

Created attachment 542459 [details]
running isntance

Comment 2 Aziza Karol 2011-12-08 10:24:16 UTC

Created attachment 542461 [details]
system log

Comment 3 wes hayutin 2011-12-08 14:09:37 UTC

lets work on this together

Comment 4 Shveta 2011-12-23 14:42:29 UTC

Able to ssh to running instances 

rpm -qa|grep aeolus
aeolus-conductor-0.8.0-0.20111222233342gitd98cb57.el6.noarch
aeolus-all-0.8.0-0.20111222233342gitd98cb57.el6.noarch
aeolus-conductor-daemons-0.8.0-0.20111222233342gitd98cb57.el6.noarch
rubygem-aeolus-image-0.3.0-0.20111222173411gitc13b654.el6.noarch
rubygem-aeolus-cli-0.3.0-0.20111222173356git3cd6277.el6.noarch
aeolus-configure-2.5.0-0.20111222173430git17b704a.el6.noarch
aeolus-conductor-doc-0.8.0-0.20111222233342gitd98cb57.el6.noarch

Note You need to log in before you can comment on or make changes to this bug.