Red Hat Bugzilla – Bug 835630
Bad value for ROOSTER_MAX_UNHIBERNATE in PowerManagementSubnetManager
Last modified: 2012-09-25 04:55:50 EDT
Description of problem:
When I upgrade db from 2.0 snapshot it is not completely the same as the loaded default snapshot for 2.2 It differs in value for parameter ROOSTER_MAX_UNHIBERNATE in PowerManagementSubnetManager feature.
The problem is that the value was "0" and in Grid 2.2 it's corrected to 0. But this correction is not part of db patches.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. load old version of db snapshot
2. upgrade db
3. compare upgraded db with default snapshot
there's some discrepancy
the feature PowerManagementSubnetManager has different value for ROOSTER_MAX_UNHIBERNATE, it's 0 in default snapshot whilst in upgraded db it's "0".
no differences were found
MAXJOBRETIREMENTTIME, ROOSTER_MAX_UNHIBERNATE, SCHEDD_PREEMPTION_RANK all had their values changed on their respective features from "0" (a value) to 0 (use default) in the db and patch files. The values have been rest to the original "0".
On all params, the default parameter value was sane but the change on the features should not have occurred.
Fixed upstream on master.
The value for MAXJOBRETIREMENTTIME, ROOSTER_MAX_UNHIBERNATE, SCHEDD_PREEMPTION_RANK is changed back to "0".