Bug 968818 - pmchart in archive mode displays wrong metric after deleting a plot and adding a new plot
Summary: pmchart in archive mode displays wrong metric after deleting a plot and addin...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: pcp
Version: el6
Hardware: Unspecified
OS: Linux
high
high
Target Milestone: ---
Assignee: pcp-maint
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-05-30 03:48 UTC by Mark Goodwin
Modified: 2020-11-30 15:12 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-11-30 15:12:12 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
pmchart showing the wrong metric values being plotted (27.32 KB, image/png)
2013-05-30 03:48 UTC, Mark Goodwin
no flags Details
PCP archive tarball from repro recipe (320.19 KB, application/x-gzip)
2017-05-03 07:18 UTC, Mark Goodwin
no flags Details

Description Mark Goodwin 2013-05-30 03:48:52 UTC
Created attachment 754636 [details]
pmchart showing the wrong metric values being plotted

Description of problem:
In archive mode, deleting a plot from an existing chart and then adding a new plot for a different metric, displays the metric values from the deleted plot, not the values from the new metric.

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

How reproducible: always

Steps to Reproduce:
1. In archive mode, delete a plot from an existing chart (e.g. delete mem.util.free from a chart showing the "Memory" view)
2. add a new plot to the same chart for a different metric (say mem.util.dirty) 
3. move the archive position slider to refresh the charts 

Actual results:
pmchart displays the new plot with values from the deleted metric, not the new one, even though the legend and plot colors are correct

Expected results:
display the right metric values for the new plot (or use the right context if that is the root cause behind this bug)

Additional info: see attached image showing mem.util.dirty plotted using metric values from mem.util.free

Comment 1 Nathan Scott 2015-01-28 04:25:11 UTC
Move pcp-gui bugs into pcp, post-package-merge.

Comment 2 Dave Brolley 2017-03-27 18:08:00 UTC
I have been unsuccessful in reproducing this problem as reported. While attempting to do so, I thought I had run into an underlying issue when the removed metric was still displayed in the metric details window (double click on the chart area). However that turned out to be a bug in the metric details window itself (fixes have been submitted for upstream review).

Perhaps with the original archive and pmchart view, I would be more successful.

Comment 3 Mark Goodwin 2017-05-03 07:18:17 UTC
Created attachment 1275840 [details]
PCP archive tarball from repro recipe

Comment 4 Mark Goodwin 2017-05-03 07:27:33 UTC
1. unpack the archive (attached to this BZ)
$ tar xf 20170502.tgz          

2. create two charts showign the same Memory view
$ pmchart -O-0 -a 20170502.06.55 -geometry 512x1024 -c Memory -c Memory
Observe in both charts that mem.util.free (green) is about 0.25GB and mem.util.other is about 6GB.

3. left-click in the bottom chart to make it current, then Edit/Chart and delete the plot for mem.util.other

4. Now observe that mem.util.free (in green) is now showing about 7GB free in the bottom chart, which is
what used to be mem.util.other (compare this with the unchanged top chart).

i.e. the wrong metric is being displayed for mem.util.free after deleting the plot for mem.util.other.

There are other ways to repro this too, but the above seems reliable

Comment 5 Ben Cotton 2020-11-05 16:46:00 UTC
This message is a reminder that EPEL 6 is nearing its end of life. Fedora will stop maintaining and issuing updates for EPEL 6 on 2020-11-30. It is our policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of 'el6'.

Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later EPEL version.

Thank you for reporting this issue and we are sorry that we were not able to fix it before EPEL 6 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged  change the 'version' to a later Fedora version prior this bug is closed as described in the policy above.

Comment 6 Ben Cotton 2020-11-30 15:12:12 UTC
EPEL el6 changed to end-of-life (EOL) status on 2020-11-30. EPEL el6 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
EPEL please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.