| Summary: | Wrong error message displayed when launching image for a provider for which images are not pushed | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Retired] CloudForms Cloud Engine | Reporter: | Shveta <ssachdev> | ||||||
| Component: | aeolus-conductor | Assignee: | Matt Wagner <matt.wagner> | ||||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | wes hayutin <whayutin> | ||||||
| Severity: | high | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 1.0.0 | CC: | akarol, athomas, deltacloud-maint, slinaber, 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-08-30 17:13:09 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: |
|
||||||||
adding to ce-sprint-next adding to ce-sprint-next adding to ce-sprint removing ce-sprint-next tracker To reproduce, the image has to be built for some provider, or you won't be allowed to try to launch at all. So build for one provider, and then try to launch with a realm restricting it to another provider for which the image is not pushed. Part of the problem here is that we're showing a barrage of errors that may or may not be relevant. When I did this, I built an image for the mock provider, and tried to launch with an EC2-only realm, yet the three errors I got included a warning that it couldn't be launched on vsphere. It's correct, but probably doesn't need to be shown. So here are the 3 errors I get when I try this: "frontend: vsphere: image is not pushed to this provider account, Realm realm1 is not mapped to any provider or provider realm, ec2: image is not pushed to this provider account" The first and last one are providers that the image isn't pushed to. I'm trying to launch on EC2, and the image was only built for mock. The middle one is badly mis-stated. The realm *is* mapped to a provider, but it's not mapped to any provider I'm trying. That text might need a little cleanup. It's not clear how we should resolve this. Should we show the realm issue and the issue that it's not pushed to EC2? Or should we somehow wrap up all of these errors and just say that there were no appropriate matches? I think it's good to show the individual errors, personally. Pushed to staging repo:
commit 15867115f932002583c45eb59fb7b3e720b5c713
Author: Matt Wagner <matt.wagner>
Date: Wed Jan 25 16:59:15 2012 -0500
BZ770377 - Better formatting for deployable exceptions
Rather than combining a slew of exceptions with .join(', '), this
adds support for showing an unsorted list of errors, and uses
this to display deployment errors.
Resolves https://bugzilla.redhat.com/show_bug.cgi?id=770377
commit d719d9ea2da07a2dea975ea3cbf4afc03ed67f6c
Author: Matt Wagner <matt.wagner>
Date: Wed Jan 25 14:58:05 2012 -0500
BZ770377 - Corrects realm mapping error text
We show this error when the realm isn't mapped to any relevant
providers or provider realms, yet the text was implying that the
realm wasn't mapped to anything at all.
Part of https://bugzilla.redhat.com/show_bug.cgi?id=770377
1586711 d719d9e in aeolus-conductor-0.8.0-16 Created attachment 559600 [details]
disabled_launch_btn
Launch button is disable if the images are not pushed for both providers and if the image is not pushed for any one provider then image is launched based on priority. Verified in rpm -qa|grep aeolus aeolus-conductor-doc-0.8.0-20.el6.noarch aeolus-configure-2.5.0-11.el6.noarch aeolus-conductor-daemons-0.8.0-20.el6.noarch rubygem-aeolus-image-0.3.0-7.el6.noarch aeolus-all-0.8.0-20.el6.noarch aeolus-conductor-0.8.0-20.el6.noarch rubygem-aeolus-cli-0.3.0-7.el6.noarch |
Created attachment 549559 [details] err Description of problem: Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Added a provider account 2. Added a realm for it 3. Mapped provider account to realm 4. Launch image from UI (image is not built and pushed for it ) Message displayed :frontend: Realm us-west is not mapped to any provider or provider realm, ssachdev: image is not pushed to this provider account, Realm us-west is not mapped to any provider or provider realm Actual results: Expected results: Additional info: rpm -qa|grep aeolus aeolus-conductor-doc-0.8.0-0.20111222233342gitd98cb57.el6.noarch aeolus-configure-2.5.0-0.20111222173430git17b704a.el6.noarch rubygem-aeolus-image-0.3.0-0.20111222173411gitc13b654.el6.noarch rubygem-aeolus-cli-0.3.0-0.20111222173356git3cd6277.el6.noarch aeolus-all-0.8.0-0.20111222233342gitd98cb57.el6.noarch aeolus-conductor-0.8.0-0.20111222233342gitd98cb57.el6.noarch aeolus-conductor-daemons-0.8.0-0.20111222233342gitd98cb57.el6.noarch