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

Bug 843074

Summary: Log graph plots negative value
Product: [Retired] CloudForms Cloud Engine Reporter: Rehana <redakkan>
Component: aeolus-conductorAssignee: Tzu-Mainn Chen <tzumainn>
Status: CLOSED ERRATA QA Contact: Rehana <aeolus-qa-list>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 1.1.0CC: athomas, dajohnso, dmacpher, sseago, tzumainn
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Applications changing states from "pending" to "stopped" caused the Logs page graph to display negative values. This fix corrects the graph behavior for "pending" to "stopped" state changes. The Logs page now displays the graph correctly.
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-12-04 15:15: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
graph none

Description Rehana 2012-07-25 13:57:51 UTC
Created attachment 600306 [details]
graph

Description of problem:


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


How reproducible:


Steps to Reproduce:
1.Login to conductor
2.Launch instance
3.go to monitor --> logs
4.Enable the preety view
  
Actual results:
Observed that the graph is plotting negative values (PFA:graph.png)

Expected results:
It should plot correctly.

Additional info:
on
rpm -qa | grep aeolus
rubygem-aeolus-cli-0.6.0-0.20120723230034git2a28761.fc16.noarch
aeolus-conductor-0.11.0-0.20120725030008gitcdc50c9.fc16.noarch
rubygem-aeolus-image-0.6.0-0.20120723230037git05a815a.fc16.noarch
aeolus-conductor-doc-0.11.0-0.20120725030008gitcdc50c9.fc16.noarch
aeolus-all-0.11.0-0.20120725030008gitcdc50c9.fc16.noarch
aeolus-configure-2.7.0-0.20120723230032gitcc8302d.fc16.noarch
aeolus-conductor-daemons-0.11.0-0.20120725030008gitcdc50c9.fc16.noarch

Comment 1 Rehana 2012-08-07 13:38:10 UTC
updating the steps:

1. Run aeolus-clean up on the host machine
2 and Reinstalled Aeolus
3.build and pushed rhel6_2 to rhevm provider
4. Launched instance
5.Observed that the graph was plotting in -ve values(in Log section and also on "cloud provider" activity section)


rpm -qa | grep aeolus | sort
aeolus-all-0.13.0-0.20120803030017git5403d2a.fc16.noarch
aeolus-conductor-0.13.0-0.20120803030017git5403d2a.fc16.noarch
aeolus-conductor-daemons-0.13.0-0.20120803030017git5403d2a.fc16.noarch
aeolus-conductor-doc-0.13.0-0.20120803030017git5403d2a.fc16.noarch
aeolus-configure-2.8.0-0.20120802230032git5271be7.fc16.noarch
rubygem-aeolus-cli-0.7.0-0.20120802230034gitd64d64f.fc16.noarch
rubygem-aeolus-image-0.6.0-0.20120802230038git05a815a.fc16.noarch

test machine 
https://sgi-xe500-01.rhts.eng.bos.redhat.com/conductor/

Comment 2 Tzu-Mainn Chen 2012-08-09 14:50:59 UTC
Patch created:

http://lists.fedorahosted.org/pipermail/aeolus-devel/2012-August/011910.html

Comment 3 Scott Seago 2012-08-13 16:38:21 UTC
Pushed to master at 21273b8562a959fc7385c3fe6074657dc001127a

Comment 4 Tzu-Mainn Chen 2012-08-13 17:09:38 UTC
Pushed to 1.1:

commit 849a214641ae4060a3537255e28efac738048fd4
BZ843074 graph fix for case when deployment/instance goes from pending to stopped
(cherry picked from commit 21273b8562a959fc7385c3fe6074657dc001127a)

Comment 6 Rehana 2012-09-20 13:25:23 UTC
verified on 

rpm -qa | grep aeolus
rubygem-aeolus-image-0.3.0-12.el6.noarch
aeolus-conductor-daemons-0.13.8-1.el6cf.noarch
rubygem-aeolus-cli-0.7.1-1.el6cf.noarch
aeolus-conductor-doc-0.13.8-1.el6cf.noarch
aeolus-all-0.13.8-1.el6cf.noarch
aeolus-conductor-0.13.8-1.el6cf.noarch
aeolus-configure-2.8.6-1.el6cf.noarch

Comment 8 errata-xmlrpc 2012-12-04 15:15:18 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHEA-2012-1516.html