Bug 1118411 - ERROR message logged during storage schema upgrade should be INFO level
Summary: ERROR message logged during storage schema upgrade should be INFO level
Keywords:
Status: NEW
Alias: None
Product: RHQ Project
Classification: Other
Component: Installer, Storage Node
Version: 4.12
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
: RHQ 4.13
Assignee: Nobody
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-07-10 16:01 UTC by John Sanda
Modified: 2022-03-31 04:27 UTC (History)
1 user (show)

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

Attachments (Terms of Use)

Description John Sanda 2014-07-10 16:01:42 UTC 
Description of problem:
When the installer runs and the storage schema is upgraded, there is a message logged at ERROR level that should be logged at INFO level,

11:31:05,290 INFO  [org.rhq.cassandra.schema.VersionManager] Preparing to check storage schema compatibility.
11:31:07,006 ERROR [org.rhq.cassandra.schema.VersionManager] Storage cluster schema version:2. Required schema version: 3. Please update storage cluster schema version.
11:31:07,007 INFO  [org.rhq.cassandra.schema.VersionManager] Completed storage schema compatibility check.
11:31:07,007 INFO  [org.rhq.enterprise.server.installer.InstallerServiceImpl] Install RHQ schema updates to storage cluster.
11:31:07,008 INFO  [org.rhq.cassandra.schema.VersionManager] Preparing to install storage schema
11:31:07,269 INFO  [org.rhq.cassandra.schema.VersionManager] Installed storage schema version is 2
11:31:07,269 INFO  [org.rhq.cassandra.schema.VersionManager] Required storage schema version is 3
11:31:07,270 INFO  [org.rhq.cassandra.schema.VersionManager] Storage schema requires udpates. Updating from version 2 to version 3.
11:31:07,270 INFO  [org.rhq.cassandra.schema.AbstractManager] Applying update file: org.rhq.cassandra.schema.UpdateFile@67afe177
11:31:09,508 INFO  [org.rhq.cassandra.schema.PopulateCacheIndex] Searching for most recent hour having raw data
11:31:09,640 INFO  [org.rhq.cassandra.schema.PopulateCacheIndex] The latest hour with raw data is Thu Jul 10 11:00:00 EDT 2014
11:31:09,689 INFO  [org.rhq.cassandra.schema.PopulateCacheIndex] Preparing to update metrics_cache_index for 1349 schedules from the raw_metrics bucket
11:31:11,272 INFO  [org.rhq.cassandra.schema.PopulateCacheIndex] Finished updating metrics_cache_index for raw_metrics bucket
11:31:11,275 INFO  [org.rhq.cassandra.schema.PopulateCacheIndex] Preparing to update metrics_cache_index for 0 schedules from the one_hour_metrics bucket
11:31:11,276 INFO  [org.rhq.cassandra.schema.PopulateCacheIndex] Finished updating metrics_cache_index for one_hour_metrics bucket
11:31:11,279 INFO  [org.rhq.cassandra.schema.PopulateCacheIndex] Preparing to update metrics_cache_index for 0 schedules from the six_hour_metrics bucket
11:31:11,279 INFO  [org.rhq.cassandra.schema.PopulateCacheIndex] Finished updating metrics_cache_index for six_hour_metrics bucket
11:31:11,289 INFO  [org.rhq.cassandra.schema.PopulateCacheIndex] The metrics cache will be come active at 2014-07-11T00:00:00.000-04:00
11:31:12,593 INFO  [org.rhq.cassandra.schema.AbstractManager] Applied update file: org.rhq.cassandra.schema.UpdateFile@67afe177
11:31:12,596 INFO  [org.rhq.cassandra.schema.VersionManager] Storage schema update org.rhq.cassandra.schema.UpdateFile@67afe177 applied.

The output for the UpdateFile needs to be fixed as well. It is using the default toString(). This is a regression that was introduced when I added to support for customer schema steps. We probably should add a toString to UpdateFile that returns the parent directory and file name, e.g., "update/0002.xml".

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


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