Bug 744713

Summary: Catalog Images page looks messy.
Product: [Retired] CloudForms Cloud Engine Reporter: Aziza Karol <akarol>
Component: aeolus-conductorAssignee: Shveta <ssachdev>
Status: CLOSED ERRATA QA Contact: wes hayutin <whayutin>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 1.0.0CC: akarol, athomas, calfonso, dajohnso, deltacloud-maint, dgao, ssachdev, sseago, thrcka
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-05-15 22:15:11 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:
Description Flags
catalog image
none
catalog image details
none
ss
none
catalog_image none

Description Aziza Karol 2011-10-10 09:34:54 UTC
Description of problem:


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


How reproducible:


Steps to Reproduce:
1.Navigate to monitor->default pool details-->Catalog Images.

see attach screen shot.

Expected results:
catalog Images page should be formatted correctly.



Additional info:
[root@dell-pesc430-03 ~]# rpm -qa | grep aeolus
rubygem-aeolus-image-0.1.0-3.20111003170706git8f23238.fc15.noarch
rubygem-aeolus-cli-0.1.0-3.20111003133323git9451323.fc15.noarch
aeolus-conductor-0.5.0-0.20111007200330gite77b251.fc15.noarch
aeolus-conductor-daemons-0.5.0-0.20111007200330gite77b251.fc15.noarch
aeolus-conductor-doc-0.5.0-0.20111007200330gite77b251.fc15.noarch
aeolus-all-0.5.0-0.20111007200330gite77b251.fc15.noarch
aeolus-configure-2.2.0-1.20111007151942git26136f2.fc15.noarch

Comment 1 Aziza Karol 2011-10-10 09:35:33 UTC
Created attachment 527198 [details]
catalog image

Comment 3 chris alfonso 2011-10-13 12:41:44 UTC
This page has been redesigned and is currently being reimplemented.

Comment 4 Aziza Karol 2011-11-18 09:11:05 UTC
The page still looks messy.
The details, the font size , spacing and the look should be in good format.
 
see attached screenshot.


[root@hp-xw8400-01 ~]# rpm -qa | egrep 'iwhd|aeolus|imagefactory'
iwhd-1.0-1.fc15.x86_64
aeolus-conductor-0.6.0-3.fc15.noarch
imagefactory-jeosconf-ec2-rhel-0.8.9-1.fc15.noarch
rubygem-aeolus-cli-0.1.0-4.fc15.noarch
aeolus-conductor-daemons-0.6.0-3.fc15.noarch
imagefactory-jeosconf-ec2-fedora-0.8.9-1.fc15.noarch
rubygem-imagefactory-console-0.5.0-4.20110824113238gitd9debef.fc15.noarch
rubygem-aeolus-image-0.1.0-6.fc15.noarch
aeolus-conductor-doc-0.6.0-3.fc15.noarch
aeolus-configure-2.3.0-1.fc15.noarch
imagefactory-0.8.9-1.fc15.noarch
aeolus-all-0.6.0-3.fc15.noarch

Comment 5 Aziza Karol 2011-11-18 09:11:53 UTC
Created attachment 534362 [details]
catalog image details

Comment 6 wes hayutin 2011-11-28 01:24:14 UTC
adding ce-sprint-next bugs to ce-sprint tracker for this release

Comment 7 Tomas Hrcka 2011-11-28 11:32:48 UTC
Fixed in commit 24fa151d8ead084bcc992f88303ef55527d7d348

Comment 8 wes hayutin 2011-12-10 17:47:49 UTC
Created attachment 544950 [details]
ss

The list of catalog entries still looks like its not styled

Comment 9 wes hayutin 2012-01-03 17:42:42 UTC
adding ce-sprint-next bugs to ce-sprint

Comment 11 Shveta 2012-02-23 05:03:55 UTC
Created attachment 565180 [details]
catalog_image

rpm -qa|grep aeolus
aeolus-conductor-daemons-0.8.0-33.el6.noarch
aeolus-configure-2.5.0-14.el6.noarch
rubygem-aeolus-image-0.3.0-8.el6.noarch
aeolus-conductor-0.8.0-33.el6.noarch
rubygem-aeolus-cli-0.3.0-9.el6.noarch
aeolus-conductor-doc-0.8.0-33.el6.noarch
aeolus-all-0.8.0-33.el6.noarch

Comment 12 Scott Seago 2012-02-29 22:12:09 UTC
I may be a little late here, but why aren't we just showing the deployables in a filtertable UI just like we do on the catalog 'show' page (where clicking through takes you to the deployable page)? That seems like it would be more consistent with the rest of the UI.

Comment 13 errata-xmlrpc 2012-05-15 22:15:11 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHEA-2012-0583.html