Bug 835630

Summary:	Bad value for ROOSTER_MAX_UNHIBERNATE in PowerManagementSubnetManager
Product:	Red Hat Enterprise MRG	Reporter:	Lubos Trilety <ltrilety>
Component:	condor-wallaby-base-db	Assignee:	Robert Rati <rrati>
Status:	CLOSED ERRATA	QA Contact:	Lubos Trilety <ltrilety>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	Development	CC:	ltoscano, matt, mkudlej, rrati
Target Milestone:	2.2
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	condor-wallaby-base-db-1.22-5	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-09-19 18:26:11 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Lubos Trilety 2012-06-26 16:13:57 UTC

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):
condor-wallaby-base-db-1.22-4

How reproducible:
100%

Steps to Reproduce:
1. load old version of db snapshot
2. upgrade db
3. compare upgraded db with default snapshot
  
Actual results:
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".

Expected results:
no differences were found

Additional info:

Comment 1 Robert Rati 2012-06-27 19:07:01 UTC

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.

Comment 3 Lubos Trilety 2012-07-20 11:52:00 UTC

Tested with:
condor-wallaby-base-db-1.22-5

The value for MAXJOBRETIREMENTTIME, ROOSTER_MAX_UNHIBERNATE, SCHEDD_PREEMPTION_RANK is changed back to "0".

>>> verified