Bug 806460

Summary: Cannot ssh into instances using ec2 m1.small or m1.medium profiles
Product: [Retired] CloudForms Cloud Engine Reporter: Richard Su <rwsu>
Component: imagefactoryAssignee: jrd <jrd>
Status: CLOSED WORKSFORME QA Contact: Martin Kočí <mkoci>
Severity: high Docs Contact:
Priority: unspecified    
Version: 1.0.0CC: akarol, brad, dajohnso, deltacloud-maint, dgao, ssachdev, whayutin
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-03-26 01:09:21 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
m1.small console output
none
ss none

Description Richard Su 2012-03-23 20:03:04 UTC
Created attachment 572371 [details]
m1.small console output

Description of problem:

Conductor reports the instance is up and running. The ssh key is also available. But will experience a timeout when you attempt to ssh into the running instance.

EC2 management console also shows state as running. But the instance fails 1 of 2 status checks.

The console output, attached to the BZ, shows a few errors during boot.


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

aeolus-configure-2.5.2-1.el6.noarch
aeolus-conductor-0.8.3-1.el6.noarch
deltacloud-core-0.5.0-8.el6.noarch
imagefactory-1.0.0rc10-1.el6.noarch
iwhd-1.5-2.el6.x86_64

How reproducible:
always

Steps to Reproduce:
1. create a deployment using small-x86_64 hwp, which will match to m1.small
2. start an instance
  
Actual results:
Instance starts up and is reported as running in conductor. But cannot ssh to it.

Expected results:
One should be able to ssh into it.

Comment 1 wes hayutin 2012-03-26 01:07:51 UTC
Created attachment 572608 [details]
ss

ssh'ing into m1.small works fine for me..

[whayutin@thinkdoe Downloads]$ ssh -i ce-3y5h7_testInstanceBackEnd_1332723450_key_70307999677400.pem root.amazonaws.com
Last login: Sun Mar 25 21:01:21 2012 from 108.83.201.51
[root@ip-10-191-81-118 ~]# 
[root@ip-10-191-81-118 ~]# 
[root@ip-10-191-81-118 ~]# wget -q -O - http://169.254.169.254/latest/dynamic/instance-identity/document
{
  "kernelId" : "aki-08ed0761",
  "ramdiskId" : null,
  "instanceId" : "i-f0d9f094",
  "billingProducts" : [ "bp-6fa54006" ],
  "instanceType" : "m1.small",
  "architecture" : "x86_64",
  "version" : "2010-08-31",
  "availabilityZone" : "us-east-1a",
  "accountId" : "673500695950",
  "imageId" : "ami-999749f0",
  "pendingTime" : "2012-03-26T00:57:33Z",
  "devpayProductCodes" : null,
  "privateIp" : "10.191.81.118",
  "region" : "us-east-1"
}[root@ip-10-191-81-118 ~]# free
             total       used       free     shared    buffers     cached
Mem:       1695484     155596    1539888          0      10184      50660
-/+ buffers/cache:      94752    1600732
Swap:            0          0

Comment 2 wes hayutin 2012-03-26 01:09:21 UTC
Richard, ping me if you still run into problems. It looks to me like you hit an issue w/ ec2, not cloud forms.