Bug 818085 - Current Alerts in instance properties page is hard coded.
Summary: Current Alerts in instance properties page is hard coded.
Keywords:
Status: CLOSED EOL
Alias: None
Product: CloudForms Cloud Engine
Classification: Retired
Component: aeolus-conductor
Version: 1.0.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: rc
Assignee: Angus Thomas
QA Contact: Rehana
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-05-02 07:44 UTC by Aziza Karol
Modified: 2020-03-27 18:03 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Embargoed:

Attachments (Terms of Use)
Alerts (231.16 KB, image/png)
2012-05-02 07:44 UTC, Aziza Karol 		no flags Details
View All

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
Note You need to log in before you can comment on or make changes to this bug.