Bug 972711 - Data migrator allows to migrate data for wrong resources
Data migrator allows to migrate data for wrong resources
Status: NEW
Product: RHQ Project
Classification: Other
Component: Monitoring (Show other bugs)
4.8
Unspecified Unspecified
unspecified Severity unspecified (vote)
: ---
: ---
Assigned To: RHQ Project Maintainer
Mike Foley
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2013-06-10 08:54 EDT by Heiko W. Rupp
Modified: 2013-06-10 08:54 EDT (History)
1 user (show)

See Also:
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: ---


Attachments (Terms of Use)

  None (edit)
Description Heiko W. Rupp 2013-06-10 08:54:41 EDT
I have a 4.7 server setup and then updated to 4.8.

Then I've removed the platform and re-imported it, so that
the old resources are gone.

Now when I run the migrator, this just adds all the old metric to C*

Where I see a potential issue is that e.g. the 4.7 DB has a resource id
range of 10000-10100 and the new import has a range from 10200-10300

Now the migrator adds data for 10000-10100 for which no schedule exists anymore,
which may fill the database and put load on the system for nothing.

Situation gets worse if the data to be migrated e.g is from yet another RHQ server that has resources in the id-range of 10000-10250, where now the new
schedule ids 10200-10250 get metric values added that do not belong to this new
resource, but to a different one - here the user will get bogus results.

The data migrator should perhaps try to validate the schedule ids and abort if the target install does not have the provided ids.

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