Bug 693706 - Providers are populated inconsistenly after clean up
Summary: Providers are populated inconsistenly after clean up
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: CloudForms Cloud Engine
Classification: Retired
Component: aeolus-conductor
Version: 0.3.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: beta
Assignee: Richard Su
QA Contact: wes hayutin
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-04-05 11:43 UTC by Shveta
Modified: 2012-01-26 12:25 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-04-05 18:05:43 UTC

Attachments (Terms of Use)
ec2_us_west_1 (92.85 KB, image/png)
2011-04-05 11:47 UTC, Shveta 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Shveta 2011-04-05 11:43:00 UTC 
Description of problem:


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


How reproducible:


Steps to Reproduce:
1.aeolus-configure
2.Two providers are populated ec2-us-east-1 and mock.
3.aeolus-cleanup and aeolus-configure
4. ec2-us-west-1 is populated as provider .
Actual results:


Expected results:


Additional info:

 rpm -qa|grep aeolus
aeolus-conductor-doc-0.0.3-0.fc14.20110401225256git6800ed8.x86_64
aeolus-configure-2.0.0-5.fc14.20110401173241git4d62feb.noarch
aeolus-conductor-debuginfo-0.0.3-0.fc1420110326042517git943202e.x86_64
aeolus-conductor-0.0.3-0.fc14.20110401225256git6800ed8.x86_64
aeolus-conductor-daemons-0.0.3-0.fc14.20110401225256git6800ed8.x86_64
Comment 1 Shveta 2011-04-05 11:47:52 UTC 
Created attachment 489968 [details]
ec2_us_west_1
Comment 2 Shveta 2011-04-05 11:48:42 UTC 
Re-run aeolus-configure populates all (the rest)
Comment 3 wes hayutin 2011-04-05 18:05:35 UTC 
providers are getting added to the conductor in a very hacky way in the configure script. I dont think they can guarantee the order in which the providers are listed.  We only need to make sure us-east/us-west/mock are all there.

closing not a bug
Comment 4 wes hayutin 2011-12-08 13:54:58 UTC 
perm close
Note You need to log in before you can comment on or make changes to this bug.