Launching instances using an image in Conductor resulted in the instance status freezing in a "New" state. This was caused by an incorrectly sized column in the database that caused an exception in the rescue block to be raised, preventing the status to change to the "create_failed" state. This update fixes the migration failed state and the status now properly changes to "Create_failed" when the instance fails.
Description of problem:
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Login to conductor
2.Build,push image to ec2
3.remove ami from EC2 console
4.launch instance using the image on conductor
Instance status is stuck in 'New' state
It should go to "create_failed" state
: INSERT INTO "events" ("created_at", "deleted_at", "status_code", "updated_at", "summary", "event_time", "source_type", "description", "source_id") VALUES ('2012-10-05 09:56:25.226744', NULL, 'deployment_launch_failed', '2012-10-05 09:56:25.226744', 'Failed to launch deployment', '2012-10-05 09:56:25.000000', 'Deployment', 'Match not found: jprovazn-ec2-test02/rhel62-rhem: RPrivate_Cloud: Frontend Cloud
Resource Cluster Ecluster is not mapped to an applicable Cloud Resource Provider or Provider Realm, jprovazn-ec2-test02/rhel62-rhem: mock: Cloud Resource Provider must be enabled, jprovazn-ec2-test02/rhel62-rhem: VPrivate_cloud: Image is not pushed to this Cloud Resource Provider Account', 17) RETURNING "id"
rpm -qa | grep aeolus
I think we should fix this for 1.1 release. It should be simple
this is caused by too short column in DB, and an exception in rescue block is raised (so create_failed state is not set properly.
*** Bug 861408 has been marked as a duplicate of this bug. ***
a patch sent: https://github.com/aeolusproject/conductor/pull/110
pushed both to master and 1.1, 1.1 commit is: 7245cbf059eb67e97bf233b39829573522ce5d1c
Retested, Instance status changed to create_failed
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.