Bug 789102

Summary: unable to launch imported images via webui.. in conductor
Product: [Retired] CloudForms Cloud Engine Reporter: wes hayutin <whayutin>
Component: aeolus-conductorAssignee: Martyn Taylor <mtaylor>
Status: CLOSED ERRATA QA Contact: wes hayutin <whayutin>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 1.0.0CC: akarol, deltacloud-maint, hbrock, matt.wagner, mtaylor, slinaber, ssachdev, sseago
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
URL: https://qeblade30.rhq.lab.eng.bos.redhat.com/conductor/deployables/11
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-05-15 22:36:30 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 wes hayutin 2012-02-09 20:11:50 UTC
Description of problem:

1. import a rhevm/vsphere image 
2. create an auto generated deployable
3. try to launch

button is disabled..


[root@qeblade30 ~]# rpm -qa | grep deltacloud
deltacloud-core-rhevm-0.5.0-5.el6.noarch
deltacloud-core-ec2-0.5.0-5.el6.noarch
rubygem-deltacloud-client-0.5.0-2.el6.noarch
deltacloud-core-0.5.0-5.el6.noarch
deltacloud-core-vsphere-0.5.0-5.el6.noarch
[root@qeblade30 ~]# rpm -qa | grep aeolus
aeolus-conductor-doc-0.8.0-24.el6.noarch
rubygem-aeolus-cli-0.3.0-8.el6.noarch
aeolus-all-0.8.0-24.el6.noarch
rubygem-aeolus-image-0.3.0-7.el6.noarch
aeolus-configure-2.5.0-12.el6.noarch
aeolus-conductor-0.8.0-24.el6.noarch
aeolus-conductor-daemons-0.8.0-24.el6.noarch

Comment 1 wes hayutin 2012-02-09 20:31:35 UTC
*** Bug 789105 has been marked as a duplicate of this bug. ***

Comment 2 Matt Wagner 2012-02-10 15:16:35 UTC
#789105 had a little detail on what I thought was causing it, FWIW.

Comment 3 Scott Seago 2012-02-10 15:47:50 UTC
Based on IRC discussions, this is probably as simple as setting the catalog to the first one returned for the deployable if it's not yet set:
@catalog = @deployment.catalogs.first unless @catalog

Or something similar in the place where we set the catalog in deployables_controller.

Comment 4 Matt Wagner 2012-02-10 19:23:30 UTC
Pushed to staging:

commit 359ec8b3c12e2812cf1ccba728a5f2ae8759375f
Author: Martyn Taylor <mtaylor>
Date:   Fri Feb 10 18:20:07 2012 +0000

    BZ#789102 Default to first catalog of deployable if catalog not set
    
    Signed-off-by: Matt Wagner <matt.wagner>

Comment 5 Matt Wagner 2012-02-13 16:21:16 UTC
I have just confirmed that this fix also fixes an issue where you were unable to launch newly-built images. Just waiting for it to land in brew so QE can sign off on it.

Comment 6 Steve Linabery 2012-02-14 15:42:12 UTC
359ec8b in aeolus-conductor-0.8.0-26

Comment 7 Steve Linabery 2012-02-14 18:20:17 UTC
359ec8b  ffac9c3 in aeolus-conductor-0.8.0-27

Comment 8 Shveta 2012-02-16 10:18:45 UTC
1. import a rhevm/vsphere image 
2. create an auto generated deployable
3. try to launch

Button is enabled.

rpm -qa|grep aeolus
aeolus-conductor-doc-0.8.0-27.el6.noarch
aeolus-conductor-daemons-0.8.0-27.el6.noarch
aeolus-configure-2.5.0-13.el6.noarch
rubygem-aeolus-cli-0.3.0-8.el6.noarch
aeolus-all-0.8.0-27.el6.noarch
aeolus-conductor-0.8.0-27.el6.noarch
rubygem-aeolus-image-0.3.0-7.el6.noarch

Comment 9 errata-xmlrpc 2012-05-15 22:36:30 UTC
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