Bug 773270

Summary: Unable to launch instance in new pool family
Product: [Retired] CloudForms Cloud Engine Reporter: Shveta <ssachdev>
Component: aeolus-conductorAssignee: Angus Thomas <athomas>
Status: CLOSED NOTABUG QA Contact: wes hayutin <whayutin>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 1.0.0CC: akarol, 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-01-11 16:35:36 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
instance_new_pool_family none

Description Shveta 2012-01-11 11:13:33 UTC
Created attachment 552086 [details]
instance_new_pool_family

Description of problem:


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


How reproducible:


Steps to Reproduce:
1. created a new pool family (New_pool_family)
2. created a new pool under it.
3. Created a catalog for that pool and built/pushed for a provider
4. launch instance for the new pool in new pool family .

Message displays :
frontend: There are no provider accounts associated with pool family of selected pool.
Actual results:


Expected results:


Additional info:

 rpm -qa|grep aeolus
aeolus-conductor-0.8.0-4.el6.noarch
aeolus-configure-2.5.0-2.el6.noarch
aeolus-conductor-doc-0.8.0-4.el6.noarch
aeolus-all-0.8.0-4.el6.noarch
rubygem-aeolus-cli-0.3.0-3.el6.noarch
rubygem-aeolus-image-0.3.0-2.el6.noarch
aeolus-conductor-daemons-0.8.0-4.el6.noarch

Comment 1 wes hayutin 2012-01-11 16:35:36 UTC
You also need to add the provider account to the pool..
Very confusing UI..

Comment 2 wes hayutin 2012-01-11 16:36:41 UTC
URL to add account https://qeblade32.rhq.lab.eng.bos.redhat.com/conductor/pool_families/2