Bug 789105

Summary: Launch button disabled for imported images
Product: [Retired] CloudForms Cloud Engine Reporter: Matt Wagner <matt.wagner>
Component: aeolus-conductorAssignee: Angus Thomas <athomas>
Status: CLOSED DUPLICATE QA Contact: wes hayutin <whayutin>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 1.0.0CC: akarol, athomas, deltacloud-maint, ssachdev
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-02-09 20:31:35 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Matt Wagner 2012-02-09 20:17:29 UTC 
Description of problem:
I imported an EC2 AMI via the web UI, and when I landed on the deployable page, I was unable to launch it. It looks like @catalog is nil (because it's only set if params[:catalog_id] is there) and we thus grey out the button. We show that the image is ready, though.

We either need to change the redirect to that page to include catalog_id, or we need to find another way of setting @catalog.


Version-Release number of selected component (if applicable):
HEAD as of commit 2bbd6bb57f3bedb2ac89fe6e891218da7912f55c


Steps to Reproduce:
1. Import an image (I used an EC2 AMI) via the web UI
2. Build a deployable
3. Look at launch button
  

Actual results:
Button is disabled.


Expected results:
Button is enabled, because the image is ready to launch.
Comment 1 wes hayutin 2012-02-09 20:31:35 UTC 

*** This bug has been marked as a duplicate of bug 789102 ***