Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 835443

Summary: Apply filters on provider account detail page does not function.
Product: [Retired] CloudForms Cloud Engine Reporter: Aziza Karol <akarol>
Component: aeolus-conductorAssignee: Dave Johnson <dajohnso>
Status: CLOSED CURRENTRELEASE QA Contact: Rehana <aeolus-qa-list>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 1.0.0CC: morazi
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-12-13 19:50:18 UTC Type: Bug
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
apply filters button
none
v1.1 ss none

Description Aziza Karol 2012-06-26 08:08:18 UTC 
Description of problem:


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


How reproducible:


Steps to Reproduce:
1.Add a provider account for ec2-eu-west-1. click on provdier account name.
2.click on apply filters.

  
Actual results:
apply filters button does not work.see attach screenshot.

Expected results:
should work.

Additional info:
rpm -qa | grep aeolus
aeolus-conductor-doc-0.8.31-1.el6cf.noarch
rubygem-aeolus-cli-0.3.3-2.el6_2.noarch
rubygem-aeolus-image-0.3.0-12.el6.noarch
aeolus-conductor-0.8.31-1.el6cf.noarch
aeolus-conductor-daemons-0.8.31-1.el6cf.noarch
aeolus-configure-2.5.9-1.el6cf.noarch
aeolus-all-0.8.31-1.el6cf.noarch
Comment 1 Aziza Karol 2012-06-26 08:09:13 UTC 
Created attachment 594391 [details]
apply filters button
Comment 2 Dave Johnson 2012-07-26 14:31:25 UTC 
Created attachment 600526 [details]
v1.1 ss

Ultimately I believe this occurs becuase the actual filters are greyed out, at least that is what the screenshot seems to show.

Checking on a box with current v1.1 rpms shows it is now fixed:
[root@sgi-xe500-01 ~]# rpm -qa | grep aeolus | sort
aeolus-all-0.11.0-0.20120725160025gita63325e.fc16.noarch
aeolus-conductor-0.11.0-0.20120725160025gita63325e.fc16.noarch
aeolus-conductor-daemons-0.11.0-0.20120725160025gita63325e.fc16.noarch
aeolus-conductor-doc-0.11.0-0.20120725160025gita63325e.fc16.noarch
aeolus-configure-2.7.0-0.20120725120040gitee0ff5c.fc16.noarch
rubygem-aeolus-cli-0.6.0-0.20120725120043git2a28761.fc16.noarch
rubygem-aeolus-image-0.6.0-0.20120725120046git05a815a.fc16.noarch
[root@sgi-xe500-01 ~]#