Hide Forgot
Created attachment 550661 [details] err Description of problem: Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Add a provider ec2_us_east_1 2. Add mock provider 3. Build and push image from UI 4. Launch instance All goes well. 5. Now add another provider ec2_us_west_1 and go to catalog entry and build and push again . Images are built and pushed . 6. now launch image for west . Message displayed :Realm realm_west is not mapped to any provider or provider realm, Realm realm_west is not mapped to any provider or provider realm, account_west: image is not pushed to this provider account AlThough realm is mapped to provider . Actual results: Expected results: Additional info: rpm -qa|grep aeolus aeolus-conductor-0.8.0-0.20111222233342gitd98cb57.el6.noarch aeolus-all-0.8.0-0.20111222233342gitd98cb57.el6.noarch aeolus-conductor-daemons-0.8.0-0.20111222233342gitd98cb57.el6.noarch rubygem-aeolus-image-0.3.0-0.20111222173411gitc13b654.el6.noarch rubygem-aeolus-cli-0.3.0-0.20111222173356git3cd6277.el6.noarch aeolus-configure-2.5.0-0.20111222173430git17b704a.el6.noarch aeolus-conductor-doc-0.8.0-0.20111222233342gitd98cb57.el6.noarch
adding to ce-sprint-next
adding to ce-sprint
removing ce-sprint-next tracker
I'd like to see the the deployable page showing where it's built/pushed, the realm mapping page for realm_west, and possibly the provider account list for the environment you're launching in. The way matching works, for each provider account that fails to match, we record the reason the match failed. If we find a match, then we discard all the failure reasons (since we don't care why the others didn't match if one did), but if we fail to find a match, we'd like to know, for each account, what didn't match so the user has a better chance of correcting this. You have 3 provider accounts: ec2_us_east_1 mock ec2_us_west_1 The 3 "failure reasons": :Realm realm_west is not mapped to any provider or provider realm Realm realm_west is not mapped to any provider or provider realm, account_west: image is not pushed to this provider account So it looks like you have 2 assemblies (name for the first is cut off here), one of which is failing to match based on realm, and the other is failing based on image status. One possibility is this: 1) mismatch in realm mapping and provider accounts available in this pool family/environment 2) one of the assembly images isn't pushed to the new provider
Issue is fixed . Able to build /push and launch for the provide added later. verified in rpm -qa|grep aeolus aeolus-conductor-0.8.0-5.el6.noarch aeolus-configure-2.5.0-4.el6.noarch aeolus-conductor-doc-0.8.0-5.el6.noarch aeolus-all-0.8.0-5.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-5.el6.noarch