Description of problem:


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


How reproducible:


Steps to Reproduce:
when multiple catalogs are assigned to the same zone,the first one assigned is displayed on the cloud page.

see attached screenshot. i have assigned 3 different catalogs to the same zone "aziza". In the cloud page only the first assigned catalog is displayed.
  

Expected results:
Need to handle this scenario.
if multiple catalogs are assigned them all the 3 catalogs names should be displayed.


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
aeolus-configserver-0.4.6-0.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.