Bug 800246

Summary: Better Error handling messages for quotas.
Product: [Retired] CloudForms Cloud Engine Reporter: Aziza Karol <akarol>
Component: aeolus-conductorAssignee: Angus Thomas <athomas>
Status: CLOSED EOL QA Contact: Rehana <aeolus-qa-list>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 1.0.0CC: akarol, deltacloud-maint, hbrock, ssachdev
Target Milestone: rcKeywords: FutureFeature, Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
err none

Description Aziza Karol 2012-03-06 05:49:24 UTC
Created attachment 567838 [details]
err

Description of problem:


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


How reproducible:


Steps to Reproduce:
logging this issue to track:
https://bugzilla.redhat.com/show_bug.cgi?id=796695#c8

Require better error messages for quotas.
It would be nice if the formatting for
multiple errors was a bit better and compressed.

see attached screenshot.


Additional info:
rpm -qa | grep aeolus
aeolus-configure-2.5.0-17.el6.noarch
aeolus-conductor-0.8.0-40.el6.noarch
aeolus-conductor-doc-0.8.0-40.el6.noarch
aeolus-all-0.8.0-40.el6.noarch
rubygem-aeolus-cli-0.3.0-12.el6.noarch
aeolus-conductor-daemons-0.8.0-40.el6.noarch
rubygem-aeolus-image-0.3.0-12.el6.noarch

Comment 1 Aziza Karol 2012-03-07 05:53:29 UTC
<akarol> athomas, if different catalogs are assigned to same zone.then which catalog should be displayed on the cloud page?
<athomas> akarol, I think the current behavior is to show the first one that was created
<akarol> athomas, i think we should not allow different catalogs to be assigned to same zone
<athomas> akarol, Well, catalogs are intended to become more useful in future releases.. as a way of grouping deployables which a set of users can launch
<athomas> akarol, So, potentially, we're going to have more catalogs  in future.
<athomas> akarol, And, if there was  a hard limit of one per zone, we wouldn't really need catalogs to be separate objects at all.. the list of deployables could just be a feature of the zone
<athomas> akarol, I think the problem we have at the moment is the UI showing a single catalog for a zone
<akarol> athomas, yes
<athomas> akarol, That's the default state, but there's no reason to expect users to stick with that
<akarol> may be multiple catalog names should be displayed if multiple catalogs are assigned to one zone
<athomas> akarol, Yeah.. Well we need to do some more design/thinking after 1.0.

Comment 2 Aziza Karol 2012-03-07 11:56:05 UTC
Please ignore comment 1. wrongly pasted.