Description of problem:
After launching a Deployable with a single EC2 instance the "State"
stays listed as "pending". This was done using
This was done using older Aeolus bits, prior to hitting Bug
739579 - Deployable fails to launch on EC2,
Using the EC2 dashboard I was able to log in and see the running
The key downloaded from Conductor allow access to the instance.
Version-Release number of selected component (if applicable):
Configure Conductor for EC2, attempt to launch a deployable with
at least one "Assembly" with an EC2 "Image ID"
Steps to Reproduce:
1. install previous version... (I realize this is nebulous but after
Bug 739579 my hope is that filing this bug will help confirm this
is no longer an issue.)
2. Run aeolus-configure
3. Attempt to launch deployable
Expect the state to change to running, a valid IP Address be listed
and a "Stop" instance or deployable switch to become available.
on_qa because condor has been removed.. testing w/ new feature
Instances 3 Properties
Graphic ViewFilter View
IP Address: ec2-184-73-128-223.compute-1.amazonaws.com
IP Address: ec2-50-16-6-150.compute-1.amazonaws.com
IP Address: ec2-107-20-27-153.compute-1.amazonaws.com
[root@unused ~]# rpm -qa | grep aeolus
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.