Bug 788417

Summary:	Inconsistency in deployable launch button
Product:	[Retired] CloudForms Cloud Engine	Reporter:	Shveta <ssachdev>
Component:	aeolus-conductor	Assignee:	Matt Wagner <matt.wagner>
Status:	CLOSED ERRATA	QA Contact:	wes hayutin <whayutin>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	1.0.0	CC:	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-05-15 22:27:58 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 Shveta 2012-02-08 07:52:31 UTC

Description of problem:


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. Configure aeolus for ec2 and mock
2. Cloud--> Component Outline --> Import an ec2 image 
3. New deployable from component outline , launch button will be greyed out
3. since there is no build for mock 

take another route to deployable 
Content --> Default catalog --> deployable 
Launch button is enabled
  
Actual results:


Expected results:


Additional info:

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

Comment 1 wes hayutin 2012-02-22 23:46:43 UTC

moving version to 1.0.0 .  version = found in version

Comment 4 Matt Wagner 2012-02-24 20:33:36 UTC

I can't reproduce this. If I follow the Steps to Reproduce, I can launch the image successfully. It may have been fixed in the past couple weeks. Is this still happening?

Comment 5 Shveta 2012-02-27 09:30:41 UTC

This seems to have been fixed in last few builds.
Can't reproduce the bug again.
Verifying it 

rpm -qa|grep aeolus
aeolus-conductor-0.8.0-36.el6.noarch
rubygem-aeolus-cli-0.3.0-10.el6.noarch
aeolus-conductor-daemons-0.8.0-36.el6.noarch
aeolus-configure-2.5.0-15.el6.noarch
rubygem-aeolus-image-0.3.0-10.el6.noarch
aeolus-all-0.8.0-36.el6.noarch
aeolus-conductor-doc-0.8.0-36.el6.noarch

Comment 6 errata-xmlrpc 2012-05-15 22:27:58 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