Bug 1377674 - Wrong scaling while restoring dumped xml rrds
Summary: Wrong scaling while restoring dumped xml rrds
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: rrdtool
Version: 6.8
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: rc
: ---
Assignee: Jaroslav Škarvada
QA Contact: qe-baseos-daemons
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-20 11:01 UTC by Berthold Cogel
Modified: 2017-10-27 15:08 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-10-27 15:08:57 UTC
Target Upstream Version:


Attachments (Terms of Use)
ganglia rrd file for test (14.77 KB, application/octet-stream)
2016-09-20 11:01 UTC, Berthold Cogel
no flags Details

Description Berthold Cogel 2016-09-20 11:01:01 UTC
Created attachment 1202851 [details]
ganglia rrd file for test

Description of problem: Wrong scaling while restoring dumped xml rrds. 

This happened during conversion of rrds from 32-bit rrds to 64-bit rrds for a new ganglia installation.


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


How reproducible: Each time


Steps to Reproduce:
1. rrdtool dump <test-org.rrd> > <test-org.xml>
2. rrdtool restore <test-org.xml> <test-new.rrd>
3. rrdtool dump <test-new.rrd> > <test-new.xml>

Compare <test-org.xml> and <test-new.xml>.

Actual results:

After step 1:

	<!-- Round Robin Archives -->
	<rra>
		<cf>AVERAGE</cf>
		<pdp_per_row>1</pdp_per_row> <!-- 15 seconds -->

		<params>
		<xff>5.0000000000e-01</xff>
		</params>
		<cdp_prep>
			<ds>
			<primary_value>8.9886666667e+01</primary_value>
			<secondary_value>8.4646666667e+01</secondary_value>
			<value>NaN</value>
			<unknown_datapoints>0</unknown_datapoints>
			</ds>
		</cdp_prep>
		<database>
			<!-- 2016-09-18 17:15:15 CEST / 1474211715 --> <row><v>8.2753333333e+01</v></row>
			<!-- 2016-09-18 17:15:30 CEST / 1474211730 --> <row><v>7.7713333333e+01</v></row>
			<!-- 2016-09-18 17:15:45 CEST / 1474211745 --> <row><v>9.3706666667e+01</v></row>
			<!-- 2016-09-18 17:16:00 CEST / 1474211760 --> <row><v>9.5700000000e+01</v></row>

....


After step 2: 

Mangled graphs from rrd in ganglia web frontend


After step 3:


<!-- Round Robin Archives -->	<rra>
		<cf> AVERAGE </cf>
		<pdp_per_row> 1 </pdp_per_row> <!-- 15 seconds -->

		<params>
		<xff> 5.0000000000e+00 </xff>
		</params>
		<cdp_prep>
			<ds>
			<primary_value> 8.0000000000e+00 </primary_value>
			<secondary_value> 8.0000000000e+00 </secondary_value>
			<value> NaN </value>
			<unknown_datapoints> 0 </unknown_datapoints>
			</ds>
		</cdp_prep>
		<database>
			<!-- 2016-09-18 17:15:15 CEST / 1474211715 --> <row><v> 8.0000000000e+00 </v></row>
			<!-- 2016-09-18 17:15:30 CEST / 1474211730 --> <row><v> 7.0000000000e+00 </v></row>
			<!-- 2016-09-18 17:15:45 CEST / 1474211745 --> <row><v> 9.0000000000e+00 </v></row>
			<!-- 2016-09-18 17:16:00 CEST / 1474211760 --> <row><v> 9.0000000000e+00 </v></row>

....


Expected results:

Both dump files should be identical.


Additional info:

rrdtool from Fedora 23 works as expected. Version tested is rrdtool-1.5.3-4.fc23.x86_64. Dump-Restore-Dump cylce leads to identical files.

Comment 4 Tomáš Hozza 2017-10-27 15:08:57 UTC
Red Hat Enterprise Linux 6 transitioned to the Production 3 Phase on May 10, 2017.  During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available.

The official life cycle policy can be reviewed here:
http://redhat.com/rhel/lifecycle

This issue does not appear to meet the inclusion criteria for the Production Phase 3 and will be marked as CLOSED/WONTFIX. If this remains a critical requirement, please contact Red Hat Customer Support to request a re-evaluation of the issue, citing a clear business justification.  Red Hat Customer Support can be contacted via the Red Hat Customer Portal at the following URL:

https://access.redhat.com


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