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

Bug 876920

Summary: Alert count is not getting updated on instance detail page
Product: [Retired] CloudForms Cloud Engine Reporter: Rehana <redakkan>
Component: aeolus-conductorAssignee: Angus Thomas <athomas>
Status: CLOSED EOL QA Contact: Rehana <aeolus-qa-list>
Severity: low Docs Contact:
Priority: medium    
Version: 1.1.0Keywords: Triaged
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: 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
alert_1
none
alert_2 none

Description Rehana 2012-11-15 10:00:31 UTC 
Created attachment 645545 [details]
alert_1

Description of problem:


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


How reproducible:


Steps to Reproduce:
1.Login to conductor
2.launch the instance
3.When the instance is on "New" state, stop the deltacloud-core service
  
Actual results:
Observed that the instance went to create_failed status, and alert was displayed, but the "Current Alerts" count on instance detail page was not updated.(PFA:alert_1.png,alert_2.png)

Expected results:
Alerts counts should get updated

Additional info:
rpm -qa | grep aeolus
aeolus-conductor-0.13.24-1.el6cf.noarch
aeolus-conductor-daemons-0.13.24-1.el6cf.noarch
rubygem-aeolus-cli-0.7.7-1.el6cf.noarch
aeolus-conductor-doc-0.13.24-1.el6cf.noarch
aeolus-configure-2.8.11-1.el6cf.noarch
aeolus-all-0.13.24-1.el6cf.noarch
rubygem-aeolus-image-0.3.0-12.el6.noarch
Comment 1 Rehana 2012-11-15 10:01:18 UTC 
Created attachment 645546 [details]
alert_2