Hide Forgot
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
<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.
Please ignore comment 1. wrongly pasted.