Hide Forgot
Currently we do not list the ec2 key pair name that is associated w/ an instance PROPERTIES FOR TESTKEY04 Name testkey04 Status running Public Addresses ec2-50-17-141-23.compute-1.amazonaws.com Private Addresses ip-10-202-23-91.ec2.internal Operating system Fedora 13 Provider ec2-us-east-1 Base Template template_simplenddn6 Architecture x86_64 Memory 7680.0 Storage 850.0 Instantiation Time 21-Apr-2011 13:34:49 Uptime 56.182108 Current Alerts 0 Console Connection via SSH SSH key Download Owner aeolus user Shared to N/A This make is more difficult to match the ssh key that you can download to the key listed in ec2. The ec2 console *does* list the ssh key pair name
making sure all the bugs are at the right version for future queries
adding to ce-sprint-next
adding to ce-sprint
removing ce-sprint-next tracker
Jan, Can you please investigate whether the key pair name is accessible via the DC API? If it is, this change will be in scope for CF 1.0
EC2 key pair name is same as name of instance_key in conductor. A patch sent: https://fedorahosted.org/pipermail/aeolus-devel/2012-January/008129.html
pushed, commit: 35e4ee509e18e747dfe3d191cc56bfe227c53099
aeolus-conductor-0.8.0-8.el6.src.rpm 0a815f543210b0a08f49ef5fde08b1a4f644bb11
Properties for ec2_1/ec2-frontend Name ec2_1/ec2-frontend Status running Public Addresses ec2-50-19-136-82.compute-1.amazonaws.com Private Addresses ip-10-73-89-238.ec2.internal Assembly ec2-frontend Provider ec2-us-east-1 Architecture x86_64 Memory 512 Storage Instantiation Time 19-Jan-2012 07:57:11 Current Alerts 0 Console Connection via SSH SSH key Download SSH key name ec2_1_ec2-frontend_1326959833_key_69852672656700 Owner aeolus user Shared to N/A ===================================== Key name is displayed now. Verified in rpm -qa|grep aeolus aeolus-conductor-0.8.0-8.el6.noarch aeolus-conductor-daemons-0.8.0-8.el6.noarch rubygem-aeolus-image-0.3.0-3.el6.noarch rubygem-aeolus-cli-0.3.0-4.el6.noarch aeolus-all-0.8.0-8.el6.noarch aeolus-configure-2.5.0-5.el6.noarch aeolus-conductor-doc-0.8.0-8.el6.noarch
Created attachment 556201 [details] Key_name
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHEA-2012-0583.html