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

Bug 869248

Summary: Auto refresh causes incorrect display of images in the cloud.
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.1.0CC: athomas
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: 2020-03-27 19:40:56 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
image list none

Description Aziza Karol 2012-10-23 11:51:00 UTC 
Description of problem:


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


How reproducible:


Steps to Reproduce:
1.create a new cloud "cloud Prod" and build an image in this cloud.
2.Build few images in default cloud.
3.Navigate to Administer->cloud and click on "cloud prod" name.
4.Navigate to images and wait for the page to auto refresh.



Actual results:
I have only one image build in the cloud name "cloud Prod".However the images build in default cloud is also displayed in the image list after auto refresh.

see attached screeshots.

Expected results:
Should display images only build under that cloud even after auto refresh

Additional info:
 rpm -qa | grep aeolus
aeolus-conductor-doc-0.13.20-1.el6cf.noarch
rubygem-aeolus-cli-0.7.5-1.el6cf.noarch
aeolus-all-0.13.20-1.el6cf.noarch
aeolus-conductor-0.13.20-1.el6cf.noarch
rubygem-aeolus-image-0.3.0-12.el6.noarch
aeolus-configure-2.8.9-1.el6cf.noarch
aeolus-conductor-daemons-0.13.20-1.el6cf.noarch
Comment 1 Aziza Karol 2012-10-23 11:52:01 UTC 
Created attachment 632049 [details]
image list
Comment 4 Imre Farkas 2013-01-18 10:55:35 UTC 
I wasn't able to reproduce this one: it should have been fixed along with #865548

Could you please check if this bug still exists in master?