Bug 818085

Summary: Current Alerts in instance properties page is hard coded.
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.0.0CC: dajohnso, hbrock, whayutin
Target Milestone: rcKeywords: Triaged
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
Alerts none

Description Aziza Karol 2012-05-02 07:44:02 UTC 
Description of problem:


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


How reproducible:


Steps to Reproduce:
I launched an vsphere instance which failed and alert count was 1.
Then navigate to filter view-instance and click on failed vsphere instance.

  
Actual results:
properties page displays Current Alerts: 0  which is hard coded.see attached screenshot.

Expected results:
Current Alerts should get updated with proper count.

Additional info:
rpm  -qa | grep aeolus
aeolus-configure-2.5.3-1.el6.noarch
aeolus-conductor-0.8.13-1.el6_2.noarch
rubygem-aeolus-image-0.3.0-12.el6.noarch
rubygem-aeolus-cli-0.3.1-1.el6.noarch
aeolus-all-0.8.13-1.el6_2.noarch
aeolus-conductor-doc-0.8.13-1.el6_2.noarch
aeolus-conductor-daemons-0.8.13-1.el6_2.noarch
Comment 1 Aziza Karol 2012-05-02 07:44:40 UTC 
Created attachment 581535 [details]
Alerts
Comment 2 Hugh Brock 2012-05-07 18:01:25 UTC 
Not even sure why this field is here. We should probably remove it.
Comment 3 Hugh Brock 2012-05-11 14:50:50 UTC 
Not severe enough for Z, marking as such