Description of problem: Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
master commit id: a751296 This was an issue of adding a new field and not upgrading all of the nulls to 0's if there was previous values in the db. The new fix converts the nulls to zeros and also prevents this from happening on any new values by converting the null to zero on the setters. The affected fields are: PropertyDefinitionList.min and PropertyDefinitionList.max I will move this to modified until verification of the upgrade tests.
Created attachment 618291 [details] Log from customer upgrade that went awry
+ <statement desc="Update the NULL to 0 for MAX_ENTRIES"> + UPDATE RHQ_CONFIG_PROP_DEF + SET MAX_ENTRIES = 0 + WHERE MAX_ENTRIES IS NULL + </statement> Shouldn't the default value for MAX_ENTRIES be 2147483647 (Integer.MAX_VALUE)?
You are correct Andreas. Thanks that would have manifested itself later as another bug. Cut and paste errors in the fog of war;)
Commit to master: aed6157 This latest fix sets an appropriate maximum enables fixes the test for checking failures of the database upgrade process (which was not enabled for this version RHQ4.5).
Closing as this has been implemented for a long time.