Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 727890

Summary:	UPDATE_INTERVAL is not attached to startd subsystem
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:	low	Docs Contact:
Priority:	low
Version:	Development	CC:	matt, mkudlej
Target Milestone:	2.1
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	condor-wallaby-base-db-1.15-1	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-01-27 19:12:33 UTC	Type:	---
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 2011-08-03 14:31:28 UTC

Description of problem:
There is a new parameter UPDATE_INTERVAL in wallaby base db, it should be attached to subsystem which use it, but it's not. The UPDATE_INTERVAL should be attached to startd subsystem.

Version-Release number of selected component (if applicable):
condor-wallaby-base-db-1.14-1

How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Robert Rati 2011-08-29 19:22:13 UTC

Pushed upstream on branch:
BZ727890-UPDATE_INTERVAL-stard-subsystem

Comment 3 Lubos Trilety 2011-10-25 12:02:19 UTC

Tested with:
condor-wallaby-base-db-1.16-2

Tested on:
RHEL6 x86_64, i386
RHEL5 x86_64, i386

# ccs -l -s startd | grep -i update_interval
  UPDATE_INTERVAL

>>> VERIFIED